Affects Version/s: 2.1.5
Fix Version/s: None
Environment:Weblogic 10.3.4 server,Eclipse IDE,Windows xp,Java SE 6,
JSF specification JSF_20101108 mentions in its section 3.1.5 "It is strongly
recommend that application developers place managed beans that are pointed at by component binding expressions in
"request" scope, and not any other scope."
My concerns are as follows:-
1) We are getting duplicate component id exception when using binding in a session scoped variable in myfaces 2.1.It is a well known issue.
This is a "recommendation" for the developers but has been forced by the myfaces implementation.
2) JSF 1.2 and 1.1 implementations worked fine with the binding variables in session scope also.
3) The mojarra implementation does not enforces this.
Please let me know if this issue will be taken up in future releases or myfaces is going to have the same implementaion from now on.