EJB3 Version Targets for AS 6.0 M3

[johnbailey]

What version of the various EJB3 sub-projects are targeted for AS 6.0 M3?  I have done some initial VFS3 integration on a branch based off the EJB3 trunk, but have run into some version conflicts integrating the branch into the AS.  Are there plans to upgrade the EJB3 project versions for the AS M3?  If not it may be better for me to branch the existing released versions for the initial integration for M3.

Any ideas?

[jaikiran]

For AS trunk, the module which integrates with the AS is the ejb3_1 (available at EJB3_Trunk/ejb3_1). This week we'll be releasing 1.0.1 version of that module into AS for 6.0.0.M2. (most of the) other sub-modules are EJB3  are pulled in as transitive dependencies from this module. So the appropriate versions of the other sub-modules are listed in the EJB3_trunk/ejb3_1/pom.xml.

Which sub-modules have changed in EJB3, for VFS? If for example, it's the "core" module which has changed, then usually it would mean bumping the version of core appropriately and then updating the ejb3_1/pom.xml dependency to pull in this new version.

Once M2 is out, we plan to continue our regular release cycles (twice a month). So the latest released EJB3 version, at that point in time, will be integrated in M3.

[wolfc]

Each module you see under ejb3/trunk is effectively a stand-alone component. Most of these components are re-used in multiple runtimes (EAP 5 & AS 6), so forking them is not your default option.

You need to isolate your changes into an abstract component which we can re-use to build components for multiple runtimes.

[johnbailey]

What I should have said is, whichever component versions are going to be included in AS 6.0 M3 will need to be integrated with VFS3 prior to the M3 release.

Below are all the files with references to VFS in ejb3 components:
./aop-deployers/src/main/java/org/jboss/aop/asintegration/jboss5/AOPAnnotationMetaDataParserDeployer.java
./concurrency/src/test/java/org/jboss/ejb3/concurrency/test/common/AbstractBootstrapTestCase.java
./core/src/main/java/org/jboss/ejb3/ClassFileFilter.java
./core/src/main/java/org/jboss/ejb3/ClientDescriptorFileFilter.java
./core/src/main/java/org/jboss/ejb3/DeploymentUnit.java
./core/src/main/java/org/jboss/ejb3/Ejb3Deployment.java
./core/src/main/java/org/jboss/ejb3/EJBContainer.java
./core/src/main/java/org/jboss/injection/InjectionContainer.java
./core/src/test/java/org/jboss/ejb3/test/cachepassivation/MockDeploymentUnit.java
./core/src/test/java/org/jboss/injection/test/common/DummyInjectionContainer.java
./deployers/src/main/java/org/jboss/ejb3/deployers/EjbAnnotationMetaDataDeployer.java
./embedded/src/main/java/org/jboss/ejb3/embedded/deployment/EmbeddedEjb3DeploymentUnit.java
./embedded/src/main/java/org/jboss/ejb3/embedded/dsl/DeploymentBuilder.java
./embedded/src/main/java/org/jboss/ejb3/embedded/JBossEJBContainer.java
./endpoint-deployer/src/test/java/org/jboss/ejb3/endpoint/deployers/test/simple/unit/DeployEndpointTestCase.java
./endpoint-deployer/src/test/resources/conf/bootstrap/deployers.xml
./jta-profile/src/test/java/org/jboss/ejb3/jta/profile/test/lookup/unit/LookupTransactionManagerTestCase.java
./profile3_1/src/it/common/src/main/java/org/jboss/ejb3/profile3_1/test/common/AbstractProfile3_1_TestCase.java
./profile3_1/src/it/common/src/main/java/org/jboss/ejb3/profile3_1/test/common/AbstractProfile3_1_TestCase.java
./singleton/src/test/java/org/jboss/ejb3/singleton/test/common/MockDeploymentUnit.java
./timerservice-mk2/src/test/java/org/jboss/ejb3/timerservice/mk2/test/common/AbstractTimerTestCase.java
./timerservice-quartz/src/test/java/org/jboss/ejb3/timerservice/quartz/test/simple/unit/SimpleUnitTestCase.java
./transactions/eclipse-target/tests-classes/instance/deployers.xml
./transactions/src/test/java/org/jboss/ejb3/test/tx/common/AspectDeployment.java
./transactions/src/test/resources/instance/deployers.xml 

I will take a look at all the references from tests and see if there is a way to remove the VFS reference all together.  Otherwise I will ignore any project that has a test only dependency.  I realize all the ejb3/trunk components are standalone, but as long as they are going to be integrated into AS, they will need to be updated. There may be ways we can isolate the change by reducing the number of code paths into VFS and then providing some kind of plugable adapter.  I will look into this and let you know what I see.

Below is a list of ejb3 components included by AS (the bold entries are known to reference VFS):

org.jboss.ejb3:jboss-ejb3-api:jar:3.1.0:compile
org.jboss.ejb3:jboss-ejb3-cache:jar:1.0.0:compile
org.jboss.ejb3:jboss-ejb3-common:jar:1.0.1:compile
org.jboss.ejb3:jboss-ejb3-core:jar:client:1.1.22:compile
org.jboss.ejb3:jboss-ejb3-core:jar:1.1.22:compile
org.jboss.ejb3:jboss-ejb3-deployers:jar:1.0.0:compile
org.jboss.ejb3:jboss-ejb3-endpoint:jar:0.1.0:compile
org.jboss.ejb3:jboss-ejb3-ext-api:jar:1.0.0:compile
org.jboss.ejb3:jboss-ejb3-ext-api-impl:jar:1.0.0:compile
org.jboss.ejb3:jboss-ejb3-interceptors:jar:1.0.6:compile
org.jboss.ejb3:jboss-ejb3-jpa-int:jar:2.0.0-alpha-1:compile
org.jboss.ejb3:jboss-ejb3-metadata:jar:1.0.0:compile
org.jboss.ejb3:jboss-ejb3-proxy-clustered:jar:1.0.3:compile
org.jboss.ejb3:jboss-ejb3-proxy-impl:jar:1.0.6:compile
org.jboss.ejb3:jboss-ejb3-proxy-spi:jar:1.0.0:compile
org.jboss.ejb3:jboss-ejb3-security:jar:1.0.1:compile
org.jboss.ejb3:jboss-ejb3-timerservice-spi:jar:1.0.0:compile
org.jboss.ejb3:jboss-ejb3-transactions:jar:1.0.2:compile (VFS reference in test only)

org.jboss.ejb3:jboss-ejb3_1:pom:1.0.0:compile