[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7137) MDBs dont register local-jndi-name when provided in jboss.xml

[Carlo de Wolf (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf resolved JBAS-7137.
---------------------------------

    Resolution: Rejected


The assertion isn't made on the bases of the existence of an element in the xsd.

I guess you are referring to the 'JMX Notifications' in http://www.jboss.org/community/wiki/JBossMDB of EJB 2 MDBs in AS 4.0.2. In which case we're talking about MBean names, not JNDI names.
Said construct is unsupported in EJB 3 MDBs in AS 5.

Use the forum if you want to discuss new requirements. 

> MDBs dont register local-jndi-name when provided in jboss.xml
> -------------------------------------------------------------
>
>                 Key: JBAS-7137
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7137
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-5.1.0.GA
>         Environment: WIndows, Java 1.6 huge fat fast machine with thousands of terabytes
>            Reporter: Bill Culp
>            Assignee: Carlo de Wolf
>
> MDBs do not register a JNDI name at all even when local-jndi-name is specified in the jboss.xml and can only be looked up using jboss.j2ee:jar=foo, name=fooname, service=EJB3.
> Also start stop destroy create methods as provided for EJB beans in JMX are not provided.

-- 
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