I am extremely frustrated to see the behavior that same JSF managed bean (declared as session scoped) is shared among multiple browsers. From the primitive definition of a HttpSession, every browser window action should be accompanied with a separate session. Below is the code and project setup:
Bean class source:
lib folder contents:
App Server: Apache Tomcat 7.0.16
Java Version: 1.6
Could someone please let me know whether I am making any mistakes or this is a known defect? I also came across another similar post and poster suggested using Orchestra, but session scope is a specification given by JSF and the implementation MUST properly implement it. If I choose a new technology / framework for every feature promised by JSF, then what is the point in calling JSF as a framework?
I am working on a huge framework development project which uses Hibernate 3, Spring 3 and we chose JSF 2.0 for front end. I created a separate test web project to analyze this issue.
This issue is slapping in my face and I am loosing confidence over JSF.
Thanks in advance