Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Stack Overflow by wobblycogs
, 2 years ago
WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
via Apache's JIRA Issue Tracker by Krystian Panek, 1 year ago
WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
via apache.org by Unknown author, 2 years ago
WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
via Google Groups by Jun Kudou, 1 year ago
WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
via Stack Overflow by Tom
, 1 year ago
WELD-001303: No active contexts for scope type javax.faces.flow.FlowScoped
via Stack Overflow by Thomas
, 1 year ago
WELD-001303: No active contexts for scope type javax.enterprise.context.SessionScoped
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:679) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.getProxiedInstance(ClientProxyMethodHandler.java:138) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:100) at org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43)