-
1. Re: InjectionMetaDataDeploymentAspect misuse of EJBContainer.getEnc()
asoldano Mar 23, 2010 6:15 AM (in response to wolfc)Created https://jira.jboss.org/jira/browse/JBWS-2970 and assigned to Richard as he worked on this before.
Btw, speaking of workarounds, I see no special reason why that lookup is required at deploy time; it could probably be done just when the context is actually used at runtime for injections (jbossws-common, InjectionHelper.getContext).
-
2. Re: InjectionMetaDataDeploymentAspect misuse of EJBContainer.getEnc()
ropalka Mar 24, 2010 6:33 AM (in response to wolfc)How to reproduce this issue Carlo?
I'm asking because our night run:
http://jbossws.jboss.org:8180/hudson/job/NATIVE-CORE-AS-6.0.1-SUN-JDK-6/
didn't pop up it.
-
3. Re: InjectionMetaDataDeploymentAspect misuse of EJBContainer.getEnc()
the_olo Sep 27, 2010 7:46 AM (in response to wolfc)I've hit this problem on JBoss EAP 5.1 Beta with my EJBs exposed as JAX-WS web services when I've started using @Depends (org.jboss.ejb3.annotation.Depends) annotation on some other EJBs they depend on. All EJBs reside in a single EAR.
How to take advantage of the mentioned workaround? Could you post some specific instructions/example code?
-
4. Re: InjectionMetaDataDeploymentAspect misuse of EJBContainer.getEnc()
wolfc Sep 28, 2010 8:29 AM (in response to the_olo)Please file a support case on your EAP subscription referencing this thread.
-
5. Re: InjectionMetaDataDeploymentAspect misuse of EJBContainer.getEnc()
the_olo Sep 30, 2010 9:54 AM (in response to wolfc)Thanks for the reply;
no need to anymore - I've upgraded JBossWS-CXF to 3.3.1.GA and the problem went away, without need of working around it.