- JSF 2.1.17 (Mojarra)
- Hazelcast 3.3
- JBoss EAP 6.3
Session scopedbean named
Loginwhich contain one field
- When deploying without
Hazelcast, the bean is only instantiated one time and keep its values.
- When adding Hazelcast to the application, we've noticed that the
Loginbean is deserialized at each execution phase (the memory address change, and the set email is not kept).
How we noticed
The login page was throwing "fields are empty" message while they were actually set. We then debugged more into this and found out that the bean is re-instantiated at each phase (using a PhaseListener).
Note that if we change the bean scope to request or view, the fields will be recognized, but it is not an option in the actual context.
Is Hazelcast overriding the way JSF handle session scoped bean ? If not, why is this happening ?
Edit : The bean does implement