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

[Bill Culp (JIRA)]

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

Bill Culp reopened JBAS-7137:
-----------------------------



So the assertion being m,ade is that <local-jndi-name> which is in the jboss xsd does not exist, and has never worked.

This is incorrect, it does it exist and it used to work.  Please explain the deprectation process of the defined element

<local-jndi-name> under <message-driven> before rejecting a ticket outright.

> 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