EJB3 (duplicate) configuration files in AS trunk

[jaikiran]

I see that we maintain a copy of ejb3-deployers-jboss-beans.xml and jpa-deployer-jboss-beans.xml in AS/ejb3/src/resources/META-INF. I sort of remember that we had discussed something related to these duplicate files. But i can't recollect why we let them remain in the AS. If there's no specific reason then i guess, we can get rid of them in the AS trunk and let it be pulled in from the EJB3 project? That way we don't have to keep updating that duplicate file every time the one in EJB3 project changes.

[jaikiran]

Found the JIRA https://jira.jboss.org/jira/browse/EJBTHREE-1538. Looking at the contents of the ejb3-deployers-jboss-beans.xml, i think the reason why we let it stay there was because, some of the deployers (configured in that file) belong to the AS. There's a JIRA where we plan to move the remaining EJB3 related deployers from AS to the EJB3 project. As a first step, i'm planning to refactor (and make sure no regressions are introduced in testsuites) these 2 copies of ejb3-deployers-jboss-beans.xml, such that the one in AS only has configurations for the deployers that are in AS (and will be named ejb3-as-deployers-jboss-beans.xml) and the one in core will only contain the configurations that come from EJB3 project.

[jaikiran]

jaikiran wrote:

As a first step, i'm planning to refactor (and make sure no regressions are introduced in testsuites) these 2 copies of ejb3-deployers-jboss-beans.xml, such that the one in AS only has configurations for the deployers that are in AS (and will be named ejb3-as-deployers-jboss-beans.xml) and the one in core will only contain the configurations that come from EJB3 project.

https://jira.jboss.org/jira/browse/EJBTHREE-1979