Tim,
If we always generate values of "true", shouldn't we make the defaults
also be true? It seems very confusing otherwise.
Lloyd
On Oct 13, 2008, at 2:05 PM, Tim Quinn wrote:
> Hi, Anissa.
>
> The v2 DTD certainly says the defaults for these values is "false."
> But the domain.xml that is generated when a domain is created has
> both of the values set to "true" for both v2 and v3 prelude. So I
> guess it depends on what the meaning of "default" is.
> The v2 DTD default and, in v3, the corresponding default settings on
> the config-api DasConfig interface are "false" but the effective
> default values are "true."
> - Tim
>
> Anissa Lam wrote:
>>
>> As i am reviewing the Deployment Guide and testing if the default
>> value it mentioned is correct, I notice that in v3 prelude, the
>> default value for <autodeploy-enabled> and <dynamic-reload-
>> enabled> is "false" by default.
>> If i set that to 'true', then i can see that it is written out to
>> domain.xml as
>>
>> <das-config autodeploy-enabled="true" dynamic-reload-enabled="true"
>> deploy-xml-validation="full" autodeploy-dir="$
>> {com.sun.aas.instanceRoot}/autodeploy" />
>>
>> Is this a known issue or we have changed the default value in v3 ?
>> It used to be 'true' for v2, and thats what the deployment guide
>> said also.
>>
>> thanks
>> Anissa.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>