It is just used the first '@websphere.resource-ref' tag for all different
resources and the 'res-ref-name' parameter seams not to be used.
------------------------------------------------------------------------------------------------------------------------------------------
Key: XDT-1587
URL: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1587
Project: XDoclet
Type: Bug
Components: IBM Module
Versions: 1.2.3
Environment: Windows XP
java version "1.4.2" (Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142-20040926
(JIT enabled: jitc)))
maven 1.0.2
Reporter: Johannes Höhne
Assigned to: xdoclet-devel (Use for new issues)
If I use this constellation:
* @ejb.bean
* name="SpecialStoreGroupService"
* display-name="SpecialStoreGroupService"
* type="Stateless"
* transaction-type="Container"
* jndi-name="ejb/SpecialStoreGroupService"
*
* @ejb.home
* extends="javax.ejb.EJBHome"
* local-extends="javax.ejb.EJBLocalHome"
*
* @ejb.interface
* extends="javax.ejb.EJBObject"
* local-extends="javax.ejb.EJBLocalObject"
*
* @ejb.resource-ref
* description="To put something in a queue"
* res-name="jms/QueueConnectionFactory"
* jndi-name="jms/XAQCF"
* res-type="javax.jms.QueueConnectionFactory"
* res-auth="Container"
* res-sharing-scope="Shareable"
*
* @ejb.resource-ref
* description="To put something in the ERAEventQueue"
* res-name="jms/SSG2EraEventQueueRef"
* jndi-name="jms/EraInternal2EraDispatcher"
* res-type="javax.jms.Queue"
* res-auth="Container"
* res-sharing-scope="Shareable"
*
* @ejb.resource-ref
* description="To let TREND access to the Database"
* res-name="jdbc/DataSource"
* jndi-name="DataSource"
* res-type="javax.sql.DataSource"
* res-auth="Container"
* res-sharing-scope="Shareable"
*
* @websphere.resource-ref
* res-ref-name="jms/SSG2EraEventQueueRef"
*
* @websphere.resource-ref
* res-ref-name="jms/QueueConnectionFactory"
*
* @websphere.resource-ref
* res-ref-name="jdbc/DataSource"
* isolation-level="TRANSACTION_READ_COMMITTED"
*/
I get the following result as ibm-ejb-jar-ext.xmi:
<ejbExtensions xmi:type="ejbext:SessionExtension"
xmi:id="Session_ext_3">
<enterpriseBean xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_SpecialStoreGroupService" />
<resourceRefExtensions xmi:id="ResourceRef_ext_3">
<resourceRef href="META-INF/ejb-jar.xml#ResRef_3" />
</resourceRefExtensions>
<resourceRefExtensions xmi:id="ResourceRef_ext_4">
<resourceRef href="META-INF/ejb-jar.xml#ResRef_4" />
</resourceRefExtensions>
<resourceRefExtensions xmi:id="ResourceRef_ext_5">
<resourceRef href="META-INF/ejb-jar.xml#ResRef_5" />
</resourceRefExtensions>
</ejbExtensions>
But I expect that the ResourceRef_ext_5 got the isolation level named in the
websphere.resource-ref .
It's getting funny if I use the following configuration:
* @ejb.bean
* name="SpecialStoreGroupService"
* display-name="SpecialStoreGroupService"
* type="Stateless"
* transaction-type="Container"
* jndi-name="ejb/SpecialStoreGroupService"
*
* @ejb.home
* extends="javax.ejb.EJBHome"
* local-extends="javax.ejb.EJBLocalHome"
*
* @ejb.interface
* extends="javax.ejb.EJBObject"
* local-extends="javax.ejb.EJBLocalObject"
*
* @ejb.resource-ref
* description="To put something in a queue"
* res-name="jms/QueueConnectionFactory"
* jndi-name="jms/XAQCF"
* res-type="javax.jms.QueueConnectionFactory"
* res-auth="Container"
* res-sharing-scope="Shareable"
*
* @ejb.resource-ref
* description="To put something in the ERAEventQueue"
* res-name="jms/SSG2EraEventQueueRef"
* jndi-name="jms/EraInternal2EraDispatcher"
* res-type="javax.jms.Queue"
* res-auth="Container"
* res-sharing-scope="Shareable"
*
* @ejb.resource-ref
* description="To let TREND access to the Database"
* res-name="jdbc/DataSource"
* jndi-name="DataSource"
* res-type="javax.sql.DataSource"
* res-auth="Container"
* res-sharing-scope="Shareable"
*
* @websphere.resource-ref
* res-ref-name="jdbc/DataSource"
* isolation-level="TRANSACTION_READ_COMMITTED"
*
* @websphere.resource-ref
* res-ref-name="jms/SSG2EraEventQueueRef"
*
* @websphere.resource-ref
* res-ref-name="jms/QueueConnectionFactory"
*/
Than I'll get this result:
<ejbExtensions xmi:type="ejbext:SessionExtension"
xmi:id="Session_ext_3">
<enterpriseBean xmi:type="ejb:Session"
href="META-INF/ejb-jar.xml#Session_SpecialStoreGroupService" />
<resourceRefExtensions xmi:id="ResourceRef_ext_3"
isolationLevel="TRANSACTION_READ_COMMITTED">
<resourceRef href="META-INF/ejb-jar.xml#ResRef_3" />
</resourceRefExtensions>
<resourceRefExtensions xmi:id="ResourceRef_ext_4"
isolationLevel="TRANSACTION_READ_COMMITTED">
<resourceRef href="META-INF/ejb-jar.xml#ResRef_4" />
</resourceRefExtensions>
<resourceRefExtensions xmi:id="ResourceRef_ext_5"
isolationLevel="TRANSACTION_READ_COMMITTED">
<resourceRef href="META-INF/ejb-jar.xml#ResRef_5" />
</resourceRefExtensions>
</ejbExtensions>
As you can see all resources got isolation level TRANSACTION_READ_COMMITTED. In
fact you can event omit the 'res-ref-name' Parameter event it is mandatory and
just the first @websphere.resource-ref will be used.
I'll just try to tell my boss that there is nothing better than XDoclets and we
havn't to fondle around with this massy RAD thing to click together our
descriptors so please help me to make it better soon.
Marry Christmas,
Johannes Höhne
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
xdoclet-devel mailing list
xdoclet-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
