-
30. Re: JBoss 6M2: WELD-000702 Unable to find BeanManager for org.apache.catalina.core.ApplicationContextFacade@b8c4f5
Scot Meyer wrote on Aug 18, 2010 17:12:
I have the exact same problem. Very simple JSF2.0, WELD, Tomcat 7 using FORM Authentication and get the same error org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped. Im at the point of dumping CDI as I am not sure its useful if FORM Authentication doesn't work. This seems to me to be a big hold in throwing an exception when you are trying to forward to another page on a separate session that isn't associated with the original session when the request was made. Tomcat will restore the original session after the login succeeds.I haven't considered dumping CDI, as it's a great specification. I've considered dumping Weld, as
this is a Weld implementation problem, not a CDI problem. Maybe having a look a OpenWebBeans or
implementing the authentication process manually using the new features of the Servlet 3 specification.Marcos
-
31. Re: JBoss 6M2: WELD-000702 Unable to find BeanManager for org.apache.catalina.core.ApplicationContextFacade@b8c4f5
Funny I didn't notice while I was typing CDI I was thinking Weld. Anyways it (Weld) didn't work.
I haven't even looked for other CDI implementations as I was hoping this (Weld) would work.
-
32. Re: JBoss 6M2: WELD-000702 Unable to find BeanManager for org.apache.catalina.core.ApplicationContextFacade@b8c4f5
At the risk of being accused of splitting hairs, this is actually an issue with JBoss AS, not Weld. Please remember that we haven't yet got JBoss AS to be either CDI compliant or Java EE 6 compliant - so using it comes with the disclaimer that the ride will be a little bumpy. We will have this issue fixed for our EE6 compliant 6.0.0 release.
For background, unfortunately the Servlet specification is under-specified in this area, meaning the way the various lifecycle callbacks work with form based authentication are undefined, and so we have to work with container specific hooks (this should be fixed in the next servlet spec).
-
33. Re: JBoss 6M2: WELD-000702 Unable to find BeanManager for org.apache.catalina.core.ApplicationContextFacade@b8c4f5
Pete Muir wrote on Aug 20, 2010 06:23:
We will have this issue fixed for our EE6 compliant 6.0.0 release.Thank you for saying this. I will wait.
Marcos
-
34. Re: JBoss 6M2: WELD-000702 Unable to find BeanManager for org.apache.catalina.core.ApplicationContextFacade@b8c4f5
Can anyone update the status on this issue? I'm still having the same exception when I enabled the Form Based Authentication in Tomcat 6.
Servlet.service() for servlet Faces Servlet threw exception: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScopedIs there any workaround yet or patch for this error? If anyone knows any workaround or is aware of a patch to resolve this error,
plase
respond.
Thanks,
michelle -
35. Re: JBoss 6M2: WELD-000702 Unable to find BeanManager for org.apache.catalina.core.ApplicationContextFacade@b8c4f5
It is really difficult to believe that JBoss 6 is final yet no one can build a FORM based web application that uses Weld in it because of this bug. Or am I missing something?
Marcos
-
36. Re: JBoss 6M2: WELD-000702 Unable to find BeanManager for org.apache.catalina.core.ApplicationContextFacade@b8c4f5
At the risk of being accused of splitting hairs, this is actually an issue with JBoss AS, not WeldThis problem also occurs in GlassFish 3.0.1 with the Weld CDI Implementation.
I was toying around with the idea of using JAAS with Form Based authentication and ran into the exception:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScopedIf I switch to basic authentication everything is fine.
Instead of spending time pointing fingers (or splitting hairs) I hope this gets resolved.