EJB3 project integration in AS

[jaikiran]

Right now the AS pulls in EJB3 through the "as-int" component (which is "ejb3" component + a bit more). Now that we are going to have EJB3.1 features, we will now have an "ejb3_1" component. The "ejb3_1" component is expected to bring in all other EJB3 components (like core, proxy etc...) and EJB3.1 components (like no-interface, async etc...). Basically, it brings in EJB3.1 feature set. So here are some questions:

1) What was our reason of having using "as-int" to bring in the EJB3 components in AS? I mean why not just use "ejb3" component in the component-matrix of AS?

2) What distinguishes "as-int" and the "ejb3" component? I see that "as-int" right now has "ejb3" + "metrics-deployer" + "mc-int". But probably we do not require this separate component for AS integration (see #3 below)

3) Do we really need "as-int" going forward? I mean we could use "ejb3" or "ejb3_1" in the component matrix of AS (depending on what it wants). Then any additional AS integration components(like "metrics-deployer") could probably be explicitly added in the component-matrix.

[alrubinger]

The initial idea was that "ejb3" would assemble all EJB3 components together, then "as-int" would combine what was needed in some particular target AS integration environment. As it stands these are not quite aligned.

If we were to really do it this way, there's be separate integration targets like "as-int-as5" and "as-int-as6", etc.

But thinking more on it, seems this integration is much better suited to be done in the integrataion layer itself: AS.

So I think it's fine to merge everything together into one ("ejb3"), probably kill "as-int", then tack anything else a particular AS target needs into the AS build. ie. you've got the right idea with 3).

S,
ALR

[wolfc]

For AS 6 we should beef up the ejb3 module in AS itself as the integration module.
as-int will be left behind as an deprecated artifact. Consumers should be refactored off it and consume ejb3 directly.

Originally jboss-ejb3 was meant to define the EJB 3.0 profile for Profile Service. I don't see that happening any time soon, so create an jboss-ejb3_1 for the EJB 3.1 definition in similar vain.

[wolfc]

See also: https://jira.jboss.org/jira/browse/EJBTHREE-1711.

[jaikiran]

For the profile3_1 (EJBTHREE-1711) we would need a bit more clarity from the ProfileService

[jaikiran]

Now that we are retiring "as-int", i have made some minor changes in our JIRA version naming to bring in a bit more clarity. A new version "EJB3_1 1.0.0" has been created. This corresponds to the "ejb3_1" component version. The earlier 1.1.23 (which really was the version of as-int) has been renamed to "as-int 1.1.23". Any new JIRAs that get fixed through EJB3_1 component will be using the "EJB3_1 x.x.x" naming series.

[jaikiran]

I'll be releasing 1.0.0 version of the ejb3_1 component in the next few minutes. This 1.0.0 version ejb3_1 is essentially equivalent to the 1.1.22 version of as-int which has been integrated with the AS. The sole intention of this version is to make the necessary changes in AS to move away from as-int and instead starting relying on this component for EJB3. Local testsuite run with the necessary changes in AS to bring in ejb3_1 have shown no regressions. This is being tracked here https://jira.jboss.org/jira/browse/JBAS-7531. Once this is done, we can start adding EJB3.1 specific component in "ejb3_1".