We use a double indirection layer to resolve the JNDI name for an ejb-jar/resource-ref
element and I don't see why this can't be handled by a single layer. For example, given
a javax.sql.DataSource reference in an ejb-jar like
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>TheSession</ejb-name>
...
<resource-ref>
<res-ref-name>jdbc/MyDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Contaner</res-auth>
</resource-ref>
</session>
</enterprise-beans>
</ejb-jar>
requires a jboss.xml descriptor like the following to map this to java:/DefaultDS
<jboss>
<enterprise-beans>
<session>
<ejb-name>TheSession</ejb-name>
<resource-ref>
<res-ref-name>jdbc/MyDS</res-ref-name>
<resource-name>DefaultDS</resource-name>
</resource-ref>
</session>
</enterprise-beans>
<resource-managers>
<resource-manager res-class="javax.sql.DataSource">
<res-name>DefaultDS</res-name>
<res-jndi-name>java:/DefaultDS</res-jndi-name>
</resource-manager>
</resource-managers>
</jboss>
But the resource-managers/resource-manager really only specifies res-jndi-name value.
Why not simply allow the following and drop the use of resource-managers?
<jboss>
<enterprise-beans>
<session>
<ejb-name>TheSession</ejb-name>
<resource-ref>
<res-ref-name>jdbc/MyDS</res-ref-name>
<res-jndi-name>java:/DefaultDS</res-jndi-name>
</resource-ref>
</session>
</enterprise-beans>
</jboss>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
