[jboss-jira] [JBoss JIRA] Resolved: (JBAS-8523) MappedReferenceMetaDataResolverDeployer should no longer add jndi name (dependency) in container metadata for nointerface view

Thu Oct 14 09:15:40 EDT 2010

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

jaikiran pai resolved JBAS-8523.
--------------------------------

    Fix Version/s: 6.0.0.CR1
       Resolution: Done


> MappedReferenceMetaDataResolverDeployer should no longer add jndi name (dependency) in container metadata for nointerface view
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-8523
>                 URL: https://jira.jboss.org/browse/JBAS-8523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Deployers, EJB3
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: 6.0.0.CR1
>
>
> MappedReferenceMetaDataResolverDeployer adds a jndi name "supplies" to container metadata for nointerface view session beans. This isn't required any more since the MappedReferenceMetaDataResolverDeployer construct shouldn't come into picture while resolving EJB3 jndi names, now that we have the EJB reference resolvers.
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira