EJBContainer.createEJBContainer() does not seem to scan dependent jars

[johaneltes]

Not sure this is a glassfish- or a weld issue.

I have two CDI-bases projects (both bean archives) that depend on the same third bean archive.
The first of the two projects is run as a weld unit test with weld-se. The second project uses a standard junit testcase to run tests on some EJB:s of the same project.

Project 1 and 2 both inject cdi beans from the third bean archive. Ir works fine in the weld-se-based project. The same injection (within a CDi-bean that is injected into a singleton EJB) can't be resolved by the embeddable EJB container (glassfish). As long as I only inject cdi beans of the same archive as the EJBs, all works fine.

weld-se-proj -> dpendent-cdi-archive works
ejbproj -> pendent-cdi-archive fails

Any insights would be much appreciated.

/Johan

[nickarls]

Show some more code (EAR-structure, test case etc)

[johaneltes]

I've uploaded a minimal project to reproduce to jira:

https://jira.jboss.org/jira/secure/attachment/12331251/verify-ejb-dep-problem.zip

[pmuir]

I don't recall seeing this issue in JIRA - can you provide the issue number please :-)

[johaneltes]

https://jira.jboss.org/jira/secure/attachment/12331251/verify-ejb-dep-problem.zip

[nickarls]

Issue number please. Or show me how to find the associated issue from a JIRA attachment link. I don't even think you can query for issues with attachements. And I didn't find anything releavant updated +-2 days from the estimated update date.

[johaneltes]

Ah - sorry about that.
Here it comes: https://jira.jboss.org/jira/browse/WELD-360

/Johan