[
https://jira.jboss.org/jira/browse/WELDINT-32?page=com.atlassian.jira.plu...
]
Pete Muir commented on WELDINT-32:
----------------------------------
A couple of problems here:
1) Weld-jboss-int is not properly detecting the no-interface view EJB as an EJB, but
instead as a managed bean. We are waiting on confirmation of no-interface view support in
trunk before fixing this
2) Weld is using the wrong prefix for the TimerService lookup (and probably others too)
https://jira.jboss.org/jira/browse/WELD-385
Injectiing TimerService or Session context fails
------------------------------------------------
Key: WELDINT-32
URL:
https://jira.jboss.org/jira/browse/WELDINT-32
Project: Weld Integration
Issue Type: Bug
Components: JBoss EJB 3.0 integration
Environment: Windows Vista x86_64, JDK1.6.0_17
Reporter: Nikolay Elenkov
Assignee: Pete Muir
Injection using @Resource fails with this exception:
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)
Code:
@Stateless
public class AsyncTest {
@Resource
private TimerService timerService;
@Resource
private SessionContext sessionContext
According to Nicklas Karlsson this is a 'bug in the integration where JBoss reports
to Weld on which EJB:s are available where' (see forum link)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira