Error injecting TimerService

[kapitanpetko]

I was about to try the new EJB 3.1 Timer features, but I am getting this error on JBoss 6.0 M1:

java.lang.RuntimeException: Error resolving property asyncTest against base null
     org.jboss.weld.el.AbstractWeldELResolver.getValue(AbstractWeldELResolver.java:120)
     org.jboss.weld.integration.webtier.jsf.ForwardingELResolver.getValue(ForwardingELResolver.java:51)
     javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
     com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
...
caused by
java.lang.RuntimeException: Error looking up java:/comp/env/weldtest.weldjsf.AsyncTest/timerService in JNDI
     org.jboss.weld.injection.spi.helpers.AbstractResourceServices.resolveResource(AbstractResourceServices.java:38)
     org.jboss.weld.util.Beans.injectEEFields(Beans.java:692)
     org.jboss.weld.bean.ManagedBean$1$1.proceed(ManagedBean.java:218)
     org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:51)
...

The code is pretty standard:

@Named
@Stateless
public class AsyncTest {

    @Resource
    private TimerService timerService;
...
}

Is this a bug in Weld or I am missing something?

[kapitanpetko]

I tried removing @Named and @Inject-ing into another bean, but the result is the same.

[nickarls]

I wouldn't be sure sure 6.0 M1 has EJB 3.1

[nickarls]

It appears as some 3.1 functionality would go into M2

[kapitanpetko]

Well, the app deploys fine, so at least some stubs are in place. The TimerService has some new methods in 3.1, but is not new. The problem is I am not even calling anything, it is injection that fails. @Resource TimerService timerService works in EJB 3.0, so it should work with Weld. I don't have JBoss here, but I am pretty sure it is not bound to java:/comp/env/weldtest.weldjsf.AsyncTest/timerService.

[nickarls]

Can you check with the console if it is in JNDI where you expect it?

[kapitanpetko]

According to the spec:

The container must make the TimerService interface available either through 
injection using the Resource annotation or in JNDI under the name java:comp/TimerService, 

It is not in java:comp/TimerService, so it should be with @Resource. I also tried injecting
SessionContext but I get the same error:

java.lang.RuntimeException: Error looking up java:/comp/env/weldtest.weldjsf.AsyncTest/sessionContext in JNDI
     org.jboss.weld.injection.spi.helpers.AbstractResourceServices.resolveResource(AbstractResourceServices.java:38)

Apparently Weld is treating those as if they were 'normal' beans, but they are container-provided, so I think this wrong?

One more thing, this is a WAR (created with the Weld JSF archetype), so maybe this is the problem? I haven't read
the whole spec (JSR 318, it is huge!), but if one can have EJB's in a WAR, the expected container services should be accessible.

So the question still stands, is this a bug in Weld or JBoss?

Will try GF when I get some time.

[kapitanpetko]

Both @Resource TimerService timerService and @Resource SessionContext sessionContext work on GF (same war).

[nickarls]

If JBoss really ties the TimerService to java:comp/Timerservice correctly, it appears to be a bug in the integration where JBoss reports to Weld on which EJB:s are available where. Could you please file a JIRA?

[kapitanpetko]

I checked JBoss 4.2 and 5.1: neither have it at java:comp/Timerservice, but injection with @Resource works. Maybe I wasn't clear earlier: JBoss 6.0 M1 doesn't have it at java:comp/Timerservice either. That shouldn't a problem though: 4.2 and 5.1 work fine without the JNDI entry.

Will file a JIRA with JBoss 6.

Thanks.

[kapitanpetko]

JBAS-7627

[kapitanpetko]

Nikolay Elenkov wrote on Jan 18, 2010 10:23:


JBAS-7627

I wasn't aware that Weld integration is a separate project. The JIRA is now WELDINT-32