Using WebBeans EJB integration in EEJB

[pmuir]

I'd like to start a discussion on this.

First, we'll need an EEJB release that contains these MC beans:

• PersistenceUnitDependencyResolver
  
• EjbReferenceResolver
  
  and the second issue to address is that to run the EJB discovery, we need to set the deployment unit in use onto the discovery used. Can we inject the DU somehow?

[alrubinger]

We're currently defining EjbReferenceResolver in ejb3-deployers-jboss-beans, which resides in ejb3-core.

Lately we've been discussing moving to finer-grained MC Deployable XMLs, to live in the same component that defines them.

So I could envision a ejb-resolver-jboss-beans.xml, pu-resolver-jboss-beans.xml - which could be used both in AS and Embedded.

S,
ALR

[wolfc]

The underlying problem is that we don't have a (JTA) data source deployer in E-EJB3.

jta-profile needs to move down the food chain. jpa-profile needs to be created and we need a simple jca-profile for the above. Then ejb3-embedded should be based on profile3_1 and your set to go.

[alrubinger]

But we don't need a full profile3_1 just to get a couple MC Beans installed into Embeddable.

This can even be done by way of jboss-ejb3. So long as there's some component that brings in the configs needed...

S,
ALR

[alesj]

and the second issue to address is that to run the EJB discovery, we need to set the deployment unit in use onto the discovery used. Can we inject the DU somehow?

See how I do this in WebBeansBootstrapDeployer.

[pmuir]

"wolfc" wrote:
The underlying problem is that we don't have a (JTA) data source deployer in E-EJB3.

jta-profile needs to move down the food chain. jpa-profile needs to be created and we need a simple jca-profile for the above. Then ejb3-embedded should be based on profile3_1 and your set to go.

For now Web Beans can manage without the PU resolver as that is a small area of functionality (for the WB tests, not for a WB user of course).

"ALRubinger" wrote:
We're currently defining EjbReferenceResolver in ejb3-deployers-jboss-beans, which resides in ejb3-core.

This one is more urgent, as we have many tests relating to EJB functionality.

See how I do this in WebBeansBootstrapDeployer.

Thanks, I forgot to look there.

[alrubinger]

"ALRubinger" wrote:
We're currently defining EjbReferenceResolver in ejb3-deployers-jboss-beans, which resides in ejb3-core.

This one is more urgent, as we have many tests relating to EJB functionality.

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

S,
ALR