No problem. The Spring MVC integration that was outlined in the blog post was easy enough for me, so I haven't tried GWT-SL. IsSerializable was a good workaround, so I didn't pursue it further.
-- Arthur Kalmenson On Wed, Jan 14, 2009 at 2:15 PM, Sumit Chandel <[email protected]> wrote: > Thanks for the info, Arthur. > > It could be possible that there is some custom stuff that Spring is doing to > Seralizable objects that causes the serialization error. Perhaps that's one > of the issues that the GWT-SL library tries to sidestep. Using > IsSerializable instead sounds like a reasonable workaround if that is indeed > the case. > > Cheers, > -Sumit Chandel > > On Tue, Jan 13, 2009 at 7:28 AM, Arthur Kalmenson <[email protected]> > wrote: >> >> Hi Sumit, >> >> I'm not using any third party libraries. I basically followed this >> blog post: >> http://blog.digitalascent.com/2007/11/gwt-rpc-with-spring-2x_12.html >> with a minor modification of making GwtRcpEndPointHandlerAdapter >> implement ServletContextAware and not replacing '.' with '/'. I found >> that when I tried to send custom java.io.Serializable objects to >> Spring MVC, I was getting an error saying the object is not >> serializable. When I switched them to be IsSerializable, it magically >> started working. I can try to recreate the issue if you want but it >> really wasn't a big deal using IsSerializable instead. >> >> -- >> Arthur Kalmenson >> >> >> >> On Mon, Jan 12, 2009 at 7:54 PM, Sumit Chandel <[email protected]> >> wrote: >> > Hi Arthur, >> > >> > I'm curious about why java.io.Serialization wouldn't work using Spring >> > MVC. >> > Did that occur when trying to work with Spring MVC directly (i.e. no >> > other >> > third party library, such as GWT-SL)? I just want to make sure there >> > wasn't >> > anything introduce by the switch to java.io.Serializable that would >> > cause >> > unexpected problems with other frameworks. >> > >> > Thanks, >> > -Sumit Chandel >> > >> > On Sun, Jan 11, 2009 at 3:47 PM, Arthur Kalmenson >> > <[email protected]> >> > wrote: >> >> >> >> If you're integrating with Spring MVC, I found problems using >> >> java.io.Serializable. Switching to IsSerializable fixed the problems. >> >> >> >> -- >> >> Arthur Kalmenson >> >> >> >> >> >> >> >> On Fri, Jan 9, 2009 at 7:17 AM, tomekp <[email protected]> wrote: >> >> > >> >> > hi, >> >> > According to GWT documentation (http://code.google.com/support/bin/ >> >> > answer.py?hl=en&answer=78126), it should be possible to use >> >> > java.io.Serializable instead of IsSerializable interface. >> >> > But for me even the simpliest classes cannot be serialized when I >> >> > switch from IsSerializable to Serializable. >> >> > I checked that the automatically generated "whitelist" contains right >> >> > entries. I checked the hosted and web mode. >> >> > I always get the following exception: >> >> > >> >> > Caused by: com.google.gwt.user.client.rpc.SerializationException: >> >> > Type >> >> > 'ch.systemsx.cisd.openbis.generic.client.web.client.dto.X' was not >> >> > assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did >> >> > not have a custom field serializer. For security purposes, this type >> >> > will not be deserialized. >> >> > at >> >> > >> >> > >> >> > com.google.gwt.user.server.rpc.impl.LegacySerializationPolicy.validateDeserialize >> >> > (LegacySerializationPolicy.java:123) >> >> > at >> >> > >> >> > >> >> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserialize >> >> > (ServerSerializationStreamReader.java:490) >> >> > at >> >> > >> >> > >> >> > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject >> >> > (AbstractSerializationStreamReader.java:61) >> >> > at >> >> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader >> >> > $ValueReader$8.readValue(ServerSerializationStreamReader.java:131) >> >> > at >> >> > >> >> > >> >> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserializeValue >> >> > (ServerSerializationStreamReader.java:372) >> >> > at >> >> > com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:287) >> >> > ... 35 more >> >> > >> >> > For some reason always the LegacySerializationPolicy class is used. >> >> > I'm using GWT 1.5. >> >> > Any ideas what can be wrong? Has anyone succeeded to use Serializable >> >> > interface? >> >> > >> >> > Greetings >> >> > Tomek >> >> > >> >> > > >> >> > >> >> >> >> >> > >> > >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
