Description of problem:

Beans from a non-CDI module are loaded when adding the module as a dependency to a Weld deployment. However, WildFly behaves differently and does not allow this.

After discussing about this difference between EAP and WildFly at #wildfly-dev, the recommendation from Jozef Hartinger was to follow WildFly behavior which seems to be the right one.

Version-Release number of selected component (if applicable):


How reproducible:

Just try to add a non-CDI module as a dependency to a Weld deployment, and use a bean from the module in a producer method, for example.

Eg.:

ModuleSpecification moduleSpec = deployment.getAttachment(Attachments.MODULE_SPECIFICATION);
ModuleLoader moduleLoader = deployment.getAttachment(Attachments.SERVICE_MODULE_LOADER);

ModuleDependency nonCDIModuleDependency = new ModuleDependency(moduleLoader, NON_CDI_MODULE_IDENTIFIER, false, true, true, false);

moduleSpec.addUserDependency(dependency);


Steps to Reproduce:
1.
2.
3.

Actual results:

Beans from a non-CDI module are loaded even if the META-INF/beans.xml is not present inside the module.

Expected results:

Beans should be recognized/loaded only if META-INF/beans.xml is present inside the module.

Additional info:

The following repository provides all the necessary code and integration tests to see this issue in action:

https://github.com/picketlink/picketlink-as-subsystem/tree/EAP_6.2

The failing test is test.org.picketlink.as.subsystem.idm.integration.IdentityConfigurationProducerTestCase.

The test above uses a @Producer for a bean located at the non-CDI module (without the META-INF/beans.xml). In this case it will pass.

There is also a WildFly branch with the same code and tests:

https://github.com/picketlink/picketlink-as-subsystem/tree/WFLY_8

The same test fails when using this branch, which is the expected behavior.