This content has been marked as final.
Show 2 replies
-
1. Re: @EJB remote access from JSF backing bean, Resolution sho
jaikiran Sep 26, 2008 2:16 AM (in response to nschweig)"NSchweig" wrote:
I use JBoss5 CR218:07:59,000 WARN [WebEJBRemoteHandler] EJBTHREE-1289: Using legacy EjbEncInjector, because mappedName for enc "env/initBean", field "null" is null (container.environmentRefGroup.annotatedEjbReferences = [AnnotatedEJBReferenceMetaData{name=initBean,ejb-ref-type=null,link=null,ignore-dependecy=false,mapped/jndi-name=null,resolved-jndi-name=null,beanInterface=interface de.shop.statelessbeans.Initialization}]) 18:07:59,015 ERROR [TomcatDeployment] ENC setup failed java.lang.IllegalStateException: Resolution should not happen via injection container at org.jboss.web.tomcat.service.TomcatInjectionContainer.getEjbJndiName(TomcatInjectionContainer.java:621) at org.jboss.injection.EjbEncInjector.inject(EjbEncInjector.java:80) ...
I think this issue is related to https://jira.jboss.org/jira/browse/JBAS-5646. That issue has been marked as fixed in CR2. That JIRA talks about fixing the issue in servlets, not sure whether JSF managed beans were considered too. -
2. Re: @EJB remote access from JSF backing bean, Resolution sho
emuckenhuber Sep 26, 2008 3:50 AM (in response to nschweig)"NSchweig" wrote:
I use JBoss5 CR2 and I am trying to get access to an ejb from a jsf backing bean.
Basically it works also with JSF managed beans.
Are you using an .ear to package your ejb.jar and .war? If so it should work without the mappedName.