If there were a DTD, even one used only for information and not
validation, there wouldn't be this need to write out every default in
domain.xml.
June
On 09/23/08 03:31 PM, Kedar Mhaswade wrote:
>
>
> Lloyd Chambers wrote:
>> Kedar,
>>
>> The point is that it's not self-evident any more.
>
> Agreed. But that's you. Someone else would say that "Oh this domain.xml
> has lot of 'clutter'; Why do I need to know what the value of
> 'validate-atmost-once-period' is, when I accepted its default value *and*
> default behavior"?
>
> BTW, V2 had this feature of not writing defaults to domain.xml, so ...
>
>
>>
>> Lloyd
>>
>> On Sep 23, 2008, at 2:54 PM, Kedar Mhaswade wrote:
>>
>>>> If the user wants to change a value, s/he's now got to refer to *
>>>> documentation* just to remember the correct attribute name and
>>>> spelling of the attribute. And if it's wrong, maybe things blow up
>>>> (eg 'jndiname' vs 'jndi-name'). That sucks.
>>> Not really. Just try "asadmin get '*'" and you'll know. It returns all
>>> the attributes, both present and absent (and have default value) from
>>> domain.xml. So, no, user does not have to refer to documentation just
>>> for default values and names of attributes (who have default values).
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>