[jboss-jira] [JBoss JIRA] Updated: (JBAS-6820) MDBs are hard-coded to use jms-ra.rar
[
https://jira.jboss.org/jira/browse/JBAS-6820?page=com.atlassian.jira.plug...
]
Clebert Suconic updated JBAS-6820:
----------------------------------
Description:
The default rar-name should be configurable.
Most certainly we could rename jms-ra.rar to jbm-something or whatever name we choose at
that point.
JBM2 will be the default by JBoss6, and I would like to use a different name by then.
was:
We may have to deploy several resource-adapters for JBossMessaging. (Say.. remote servers,
backup-servers and other configurations).
It seems that the JNDI for Inbound is simply ignored at some level. Instead of getting the
spec Inbound from the JCA configured factory, EJB3 is hard-coding the dependency to the
resource adapter and this is not acceptable for JBoss Messaging.
MDBs are hard-coded to use jms-ra.rar
-------------------------------------
Key: JBAS-6820
URL: https://jira.jboss.org/jira/browse/JBAS-6820
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: EJB3, JCA service
Affects Versions: JBossAS-5.1.0.Beta1
Reporter: Clebert Suconic
Assignee: Carlo de Wolf
Fix For: JBossAS-6.0.0.Alpha1
The default rar-name should be configurable.
Most certainly we could rename jms-ra.rar to jbm-something or whatever name we choose at
that point.
JBM2 will be the default by JBoss6, and I would like to use a different name by then.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira