Scott Stark created WFLY-3196:
Summary: Confusing IllegalStateException: WELD-000340: A request must be
associated with the context when mixing JSF/CDI
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: CDI / Weld, JSF
Affects Versions: 8.0.0.Final
Environment: [clock-jsf-test 846]$ uname -a
Darwin scotts-imac 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014;
[clock-jsf-test 847]$ java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
Also seen with:
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
Reporter: Scott Stark
Assignee: Stuart Douglas
I have a simple web app doing injection into a JSF managed bean using @EJB. When the
managed bean lifecycle and duration is described using the JSF @ManagedBean and
@ApplicationScoped I get a "IllegalStateException: WELD-000340 ..." error when
loading the welcome page. The only workaround I have seen is to disable implicit CDI
usage, but the web app is using CDI, so that is not appropriate.
The problem seems to be a lack of understanding what is going on between the weld and jsf
containers. I understand that the JSF @ManagedBean is deprecated in favor of CDI @Named,
but it would be nice if we can provide better feedback when @ManagedBean is used along
The following git repo provides a complete test application along with the steps to cause
the error as well as how to fix it by only using CDI annotations.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira