[jboss-jira] [JBoss JIRA] Reopened: (JBAS-7004) EJB3Deployer does not use the correct MC API and ends up picking irrelevant deployments

[Brian Stansberry (JIRA)]

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

Brian Stansberry reopened JBAS-7004:
------------------------------------



> EJB3Deployer does not use the correct MC API and ends up picking irrelevant deployments
> ---------------------------------------------------------------------------------------
>
>                 Key: JBAS-7004
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7004
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: JBossAS-6.0.0.M1
>
>
> EJB3Deployer currently uses the addInput(MergedJBossMetaDataDeployer.EJB_MERGED_ATTACHMENT_NAME); API of MC deployers and expects that it will be invoked only if the MergedJBossMetaDataDeployer.EJB_MERGED_ATTACHMENT_NAME attachment is available in the deployment unit. However, this is not the right API to use. This results in the EJB3Deployer being invoked for irrelevant deployments as shown here http://lists.jboss.org/pipermail/jboss-development/2009-June/014560.html
> The MC forum thread explaining the API usage is here http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156725
>   

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