[
https://jira.jboss.org/jira/browse/JBAS-7789?page=com.atlassian.jira.plug...
]
jaikiran pai commented on JBAS-7789:
------------------------------------
The jmx name is now made deterministic. For standalone jar files, this uses the pattern:
"jboss.j2ee:service=EjbModule,module=jarname"
For EJB deployment in ear it uses this pattern:
"jboss.j2ee:service=EjbModule,ear=earname,module=jarname"
P.S: After the unique module names as per spec EE6 come into picture, i guess we can use
the "module name" to generate these jmx names. But that's for later.
Allow the default jmx name of EJB(2.x) deployments to be
deterministic
----------------------------------------------------------------------
Key: JBAS-7789
URL:
https://jira.jboss.org/jira/browse/JBAS-7789
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Deployers, EJB2
Affects Versions: JBossAS-6.0.0.M1, JBossAS-6.0.0.M2
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: JBossAS-6.0.0.M3
The fix for
https://jira.jboss.org/jira/browse/JBPAPP-2419 resulted in the default jmx
name of the EJB2 deployment, non-deterministic. Many users depend on this default jmx name
to add a dependency between deployments. For example, JBAS-7760 illustrates one such use
case. Making the default, jmx name deterministic will allow users to use this in the
<depends> element of deployments.
At the same time, care has to be taken that the original bug reported in JBPAPP-2419 is
not reintroduced as part of this change.
--
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