Aug 20th, 2012, 10:35 AM
Session-management design-issue with my JSF/Spring application
I have a session-scoped spring bean that uses a singleton-scoped spring service bean in my application.
The problem is when a user close his/her browser and reopens it: the session-scoped bean is correctly deserialized but the dependency (the spring service bean) is null, resulting in a NullPointerException when the dependency is used...
Can anyone please provide design advice on how to prevent this?
Tags for this Thread