Thanks for the quick reply. I now understand the issue. So in the gwt client side code we are using the getThreadLocalRequest().getSession() to put objects in HttpSession. But i guess those objects are gwt serializable but not java.io.serializable. Any ideas on how to resolve this ?
On Aug 5, 10:06 am, Jason Morris <[email protected]> wrote: > This complaint is coming from WebSphere, not GWT. > > By implementing IsSerializable you've said "this object may be serialized by > GWT", but you haven't > implemented normal "java.io.Serializable" to make it serializable by > WebSphere. > > Whensessionreplicationis turned on, any object in thesessionis pushed to all > other WebSphere > servers via normal Java serialization as part of each HTTP request / response > cycle. > > In short, you need to implement java.io.Serializable on these objects. > > Hope that helps. > //Jason > > kss wrote: > > We are getting java.io.NotSerializableException in one of our gwt jsr > > 286 api portlets in WebSphere Portal 6.1. This exception has started > > to surface in the logs since we enabledsessionreplicationon our > > WebSphere Portal server. The object which its complaining about has > > isSerializable interface implemented. When we dont havesession > >replicationenabled; the issue dosent occur. > > > Has anyone seen this exception in websphere environment for gwt > > portlets or have any ideas ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
