@Inject across WAR and JAR

[gboro54]

I have am attempting to deploy an ear project containing a war and a jar, both containing beans.xml(META-INF directory in jar and WEB-INF directory in war). I can't inject a bean from my jar into a class of the war. Am I missing a configuration somewhere?

[gboro54]

Forgot to add I am running this on JBoss 7.1.1.Final. The archives are being built and deployed by Arquillian(if this matters).

[alesj]

I remember that by default sub-deployments didn't see each-other in AS7 .ears.

If that's not the case anymore, then no idea. If yes, that's your problem then.

Check AS7 docs if this is still true.

[gboro54]

I just had a similiar thoughts. I am working to see if adding the jboss-deployment-structure.xml will resolve the issue

[gboro54]

It seems to still be true but I am not sure how to resolve it. I am working with the jboss-deployment-strucuture right now to see if I can get it working

[gboro54]

This is not correct...according to the docs by default a war should be able to see all classed in a ejb jar packaged as an ear:

https://docs.jboss.org/author/display/AS71/Developer+Guide#DeveloperGuide-WARClassLoading

Any other thoughts?

[gboro54]

This seems to be directly releated to Arquillian handling the deployment

Michael Weiss wrote:

This is not correct...according to the docs by default a war should be able to see all classed in a ejb jar packaged as an ear:

https://docs.jboss.org/author/display/AS71/Developer+Guide#DeveloperGuide-WARClassLoading

Any other thoughts?

[alesj]

What exactly is the error?

Or, can you try the latest Weld_Core master?

(from https://github.com/weld/core -- "mvn clean install -Pupdate-jboss-as" updates the AS7;

see jboss-as/jboss-as-7/build.properties for jboss.home prop)

[alesj]

This seems to be directly releated to Arquillian handling the deployment

Why? How?

[gboro54]

If I build the project regularly, and deploy the ear(which the war has a bean at startup inject a bean from the jar and run the logic), everything works correctly. However if I build the ear using Arquillian I cannot do this. Therefore via process of elimnation the Arquillian built application must be wrong even though they look identical. Perhaps I have misconfigured the Arquillian build but it is releated to that...

Ales Justin wrote:

This seems to be directly releated to Arquillian handling the deployment

Why? How?

[alesj]

If you only need to deploy to AS7, w/o testing, there is a jboss-deploy mvn plugin, which uses management API directly.

For the failing test, it would be useful to know (for other ARQ, CDI users) why .ear doesn work ... ;-)