Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: EE-3.3.0.GA_P03, EE-4.2.0.GA
-
Fix Version/s: 4.3, EE-3.3.0.GA_P07
-
Component/s: Framework
-
Labels:None
-
Environment:myfaces
-
Support Case References:Support Case 14314:-https://icesoft.my.salesforce.com/5000g00001sOqfK?srPos=0&srKp=500
Description
{code}
...
@ManagedBean(
eager = true
)
@ViewScoped
public class IcefacesBeanDestroyRecorder implements Serializable {
....
{code}
note that https://docs.oracle.com/javaee/7/api/javax/faces/bean/ManagedBean.html
states that eager=true for ManagedBean is only available when @ApplicationScoped. The server does not actually try to make it eager, but with Myfaces, there is a server log warning printed. This is an annoyance rather than functional issue.
...
@ManagedBean(
eager = true
)
@ViewScoped
public class IcefacesBeanDestroyRecorder implements Serializable {
....
{code}
note that https://docs.oracle.com/javaee/7/api/javax/faces/bean/ManagedBean.html
states that eager=true for ManagedBean is only available when @ApplicationScoped. The server does not actually try to make it eager, but with Myfaces, there is a server log warning printed. This is an annoyance rather than functional issue.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Show
Mircea Toma
added a comment - Already explained this here: http://jira.icesoft.org/browse/ICE-11105?focusedCommentId=63807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-63807
The warning "The managed-bean with name icefacesBeanDestroyRecorder must be application scoped to support eager=true." is an oversight in Myfaces implementation of AbstractFacesInitializer because you can definitely can have an eagerly initialised view scoped bean. It's actually a feature that we rely on.
So the warning should be ignored.
Show
Ken Fyten
added a comment - The warning "The managed-bean with name icefacesBeanDestroyRecorder must be application scoped to support eager=true." is an oversight in Myfaces implementation of AbstractFacesInitializer because you can definitely can have an eagerly initialised view scoped bean. It's actually a feature that we rely on.
So the warning should be ignored.
Assign to Mircea to review and confirm that this class should be in viewscope vs. application, and make appropriate changes to the eager = true, etc.