I'm a bit surprised that this test has started failing only now,
consistently. I had a quick look at the code and the testcase. The test
is simple, it deploys a @Startup @Singleton which has a:
private BeanManager beanManager;
The weld integration DUP in AS7 sets up a BinderService for
java:comp/BeanManager which is backed by a ManagedReferenceFactory which
uses the BeanManagerService to return the BeanManager. However, the
BeanManager BinderService has _no_ dependency on the BeanManagerService
which obviously can lead to the problem that's being encountered in this
test where the ENC binding is available but the underlying
ManagedReferenceFactory can't find the BeanManagerService in the
ServiceRegistry and returns a null.
However, adding an explicit dependency for BeanManagerService on the
BinderService leads to a circular dependency in the following fashion:
jndiDepdencyService -> java:comp/BeanManager binder service ->
BeanManagerService -> (per deployment) WeldContainer -> (back to
I guess that was the whole reason why an explicit dependency wasn't
added between the java:comp/BeanManager BinderService and the
BeanManagerService. It apparently was a kind of hack somewhere which
would allow this thing to work properly and looks like some recent
change has exposed this problem.
I can't think of a proper solution for this since I'm not sure if the
per deployment WeldContainer must depend on the jndiDependencyService
(which is a service which lets other services to depend on all JNDI
entries for the deployment to be available).
On Monday 12 November 2012 11:05 PM, ci-builds(a)redhat.com wrote:
as7-master-testsuite-ip6 - Build # 5402 - Failure:
Check console output at to view the results.
1 tests failed.
Cannot deploy: WeldJndiLookupTestCase.jar
jboss-as7-dev mailing list