[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1979) Remove duplicate MC configurations for EJB3 deployers

[jaikiran pai (JIRA)]

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

jaikiran pai resolved EJBTHREE-1979.
------------------------------------

    Resolution: Done


The integration has been completed in AS through JBAS-7472. Marking this as resolved. 

> Remove duplicate MC configurations for EJB3 deployers
> -----------------------------------------------------
>
>                 Key: EJBTHREE-1979
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1979
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: core
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: EJB3_1 1.0.1
>
>         Attachments: EJBTHREE-1979.patch
>
>
> We currently have ejb3-deployers-jboss-beans.xml in ejb3-core as well as in the AS/ejb3 module. Both these files have the same contents and just add to maintaining issues. The file actually has a combination of deployers (and other MC bean configs), some of which reside in AS and some in EJB3 project. Once the remaining deployers in AS/ejb3 have been migrated to EJB3 project as part of EJBTHREE-1538, the ejb3-deployers-jboss-beans.xml in AS/ejb3 will no longer be required. Until then the files in both these locations should not duplicate the deployer/MC bean configs. The one in ejb3-core should contain only those configs which reside in EJB3 project and the one in AS/ejb3 should contain the configs for AS/ejb3 deployers.
>  
> More related discussion can be found in referenced forum thread.

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