Packaging type of ejb3_1 component

[jaikiran]

When i created the ejb3_1 component recently, i set its packaging type to "pom" (like the earlier "ejb3" component) so that it just acts as a component which will bring in the necessary dependencies, to provide the EJB3.1 runtime. But thinking more about this and given the usecases i am running into, i think making the ejb3_1 component to "jar" packaging would be more appropriate. Right now i have some MC beans which don't really belong to individual sub-components, but really make sense at something which provides a EJB3.1 runtime (== ejb3_1 component). Changing the ejb3_1 packaging to "jar" allows me to have the MC appropriate MC bean configurations at the ejb3_1 component, instead of polluting the sub-components with these bean configurations.

Thoughts?

[wolfc]

If a MC bean is defined in some component and doesn't need any configuration, the component should provide a sensible beans.xml.

Now if we need a definition which spans multiple components it can go into ejb3_1, but it also means that ejb3_1 should have some tests that verify the integration. What you define, you must test.

[jaikiran]

For example this one http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/deployers/src/main/java/org/jboss/ejb3/deployers/metadata/processor/SetDefaultLocalBusinessInterfaceProcessorFactory.java and similar ones really don't belong to the "deployers" nor do i see it being specific to any component expect for a runtime component.

The other one which i guess should belong to the runtime component is the

<bean name="org.jboss.ejb3.EjbReferenceResolver" class="org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver"/>

Right now, it's in core.