Hello,

I've got a bit of problem here with JSF. Somehow, i get my backing bean
linked to the session, while they should be request time only.


Here is my situation

engineBean (request scope) is created by JSF (coming from a <bean>
section in config)
 it returns an array of AssignmentBean, using various information from
current user's account. Those bean are wrappers around a proprietary object
then a jsp page has a datatable showing those AssignmentBean (using a
value binding in form #{engineBean.assignments}) using HtmlOutput tags


Questions:
1) How comes those beans, which are supposed to have a request scope
only, end up stored in the session scope object
"org.apache.myfaces.custom.redirectTracker.RedirectTrackerManager"
2) How to prevent this, considering those AssignmentBean are not
serializable and will never be, and a such should never reach the
session level.

Thanks for information, currently this lead to bunch of exception when
stopping tomcat because user sessions can not be serialized anymore!

Reply via email to