I am having what appears to be an issue with saveState not working on Websphere 6. My backing bean is request scoped and my jsf is saving the state of the entire backing bean. This works perfectly on Tomcat 5.5, but when I deploy to Websphere, things seem to fall apart. Currently, my backing bean holds a reference to a DataModel (not serializable) that represents a table on my page. When I try to access this DataModel after the page is submitted, I get a null pointer on Websphere, but Tomcat seems to have no problem. Could this be due to serialization differences between Websphere and Tomcat?
Any ideas? Thanks, Geoff
