Lloyd Chambers wrote:
> Attributes with default values are not written to domain.xml, per Jerome.
>
> I think this makes life harder and more surprising for the user, but
> there are certainly good arguments for this behavior as well (such as
> keeping the confiuguration small). But it certainly forces the user
> to consult documentation of some kind to figure out what options might
> be available, if a non-default change needs to be made.
Admin Console shows you all the default value. That's one more reason
to use the console. :-)
Anissa
>
> Lloyd
>
> ..............................................
> Lloyd Chambers
> lloyd.chambers_at_sun.com
> GlassFish team, LSARC member
>
>
>
>
>
>
> On Oct 9, 2008, at 4:50 AM, Jagadish Prasath Ramu wrote:
>
>>
>> Not sure whether I am missing something.
>>
>> I do not see default valued attributes in domain.xml
>> eg:
>> <jdbc-connection-pool is-isolation-level-guaranteed="false"
>> datasource-classname="org.apache.derby.jdbc.ClientDataSource"
>> res-type="javax.sql.DataSource" name="DerbyPool">
>> <property value="1527" name="PortNumber" />
>> <property value="APP" name="Password" />
>> <property value="Jagadish" name="User" />
>> <property value="localhost" name="serverName" />
>> <property value="sun-appserv-samples" name="DatabaseName" />
>> <property value=";create=true" name="connectionAttributes" />
>> </jdbc-connection-pool>
>>
>>
>> where as in v2 :
>>
>> <jdbc-connection-pool allow-non-component-callers="false"
>> associate-with-thread="false" connection-creation-retry-attempts="0"
>> connection-creation-retry-interval-in-seconds="10"
>> connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0"
>> connection-validation-method="auto-commit"
>> datasource-classname="org.apache.derby.jdbc.ClientDataSource"
>> fail-all-connections="false" idle-timeout-in-seconds="300"
>> is-connection-validation-required="false"
>> is-isolation-level-guaranteed="false"
>> lazy-connection-association="false" lazy-connection-enlistment="false"
>> match-connections="false" max-connection-usage-count="0"
>> max-pool-size="32" max-wait-time-in-millis="60000" name="DerbyPool"
>> non-transactional-connections="false" pool-resize-quantity="2"
>> res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1"
>> steady-pool-size="8" validate-atmost-once-period-in-seconds="0"
>> wrap-jdbc-objects="false">
>> <property name="PortNumber" value="1527"/>
>> <property name="Password" value="APP"/>
>> <property name="User" value="APP"/>
>> <property name="serverName" value="localhost"/>
>> <property name="DatabaseName" value="sun-appserv-samples"/>
>> <property name="connectionAttributes" value=";create=true"/>
>> </jdbc-connection-pool>
>>
>>
>> Is this a known issue ?
>>
>> Thanks,
>> -Jagadish
>>
>>
>> ---------------------------------------------------------------------
>> 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
>