Re: [jboss-as7-dev] AS7 : Discrepency (schema vs model)
Although the xml schema elements/attributes might sometimes match with
the domain model names, but I don't think it's an requirement that they
should be the same. As long as the read-resource-description shows what
the attribute in the domain model is meant for, I think it should be fine.
-Jaikiran
On Wednesday 02 November 2011 07:13 AM, Vimal Kansal wrote:
Hi,
I found that datasource xsd defines an element like :
<xs:element name=" *driver*" type="xs:token"
minOccurs="0">
<xs:annotation>
<xs:documentation>
<![CDATA[[
An unique reference to the classloader module which
contains the JDBC driver
The accepted format is driverName#majorVersion.minorVersion
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
And the cli model defines :
[standalone@localhost:9999
data-source=java:jboss/datasources/ExampleDS] :read-resource
{
"outcome" => "success",
"result" => {
"background-validation" => undefined,
"background-validation-millis" => undefined,
"blocking-timeout-wait-millis" => undefined,
"connection-properties" => undefined,
"connection-url" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=-1",
"*driver-name*" => "h2",
"enabled" => true,
"flush-strategy" => undefined,
"idle-timeout-minutes" => undefined,
"jndi-name" => "java:jboss/datasources/ExampleDS",
"jta" => true,
"max-pool-size" => 2,
"min-pool-size" => 2,
"password" => "sa",
"pool-name" => "H2DS",
"pool-prefill" => true,
"pool-use-strict-min" => undefined,
"set-tx-query-timeout" => "false",
"share-prepared-statements" => "false",
"spy" => false,
"track-statements" => "\"NOWARN\"",
"use-ccm" => true,
"use-fast-fail" => "false",
"use-java-context" => true,
"user-name" => "sa",
"validate-on-match" => "false"
}
}
While for most other elements, xsd element and the model attribute
match, this one (i.e driver vs driver-name) seems to be bit confusing.
Thx
Vimal
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev