GWT serialization problem
Hello, in my app I faced a problem when reloading some pages. The error is: com.google.gwt.user.client.rpc.SerializationException: java.lang.RuntimeException: Unable to find class com.google.gwt.user.client.rpc.core.java.lang.Long_FieldSerializer I've downloaded gwt sources and found that error is caused by this line: Class? klass = ReflectionHelper.loadClass(typeHandlerClass); in file com/google/gwt/user/client/rpc/impl/SerializerBase.java When we navigate to the page with hyper links or enter url manually everything works perfect, the code above is working, the class is loaded. But when we hit F5 button on some pages, the exception appears. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
GWT SERIALIZATION PROBLEM
Hello Guys , I have a problem ,I want to save an object to the database. I passed the object to the server using a function. Like this http://www.easywayserver.com/blog/how-to-serializable-object-in-java-2/. But my RPC is getting failed every time. What will be the problem ? i used isSerializable marker interface for serialization. Cant we send client object to the server through RPC? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT SERIALIZATION PROBLEM
Hard to tell without seeing code or stack trace. Please provide: 1. A bit of code illustrating the main players. DTO, Service, ServiceAsync, ServiceImpl method. 2. Stack Trace for the failure. Regards, Alfredo On Wed, Apr 25, 2012 at 6:20 AM, Nitheesh Chandran nithe...@aviamatica.com wrote: Hello Guys , I have a problem ,I want to save an object to the database. I passed the object to the server using a function. Like this http://www.easywayserver.com/blog/how-to-serializable-object-in-java-2/. But my RPC is getting failed every time. What will be the problem ? i used isSerializable marker interface for serialization. Cant we send client object to the server through RPC? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- Alfredo Quiroga-Villamil AOL/Yahoo/Gmail/MSN IM: lawwton -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: OpenJPA GWT serialization problem.
I tried using em.clear(). I did this after loading and accessing my
object. I also changed my fetch type to EAGER. Sadly it still fails ;
(
-Dave
On Nov 9, 6:59 am, dparish dpar...@gmail.com wrote:
Thanks David.
I tried LAZY and EAGER. Both caused the problem.
For #2, that seems promising. There's an EntityManager clear method,
but that would affect all threads using the entity manager. Any
thoughts on how to do that detach?
On Nov 8, 8:20 pm, David Chandler drfibona...@google.com wrote:
Hi dparish,
There are three issues here:
1. GWT needs a fully populated object graph to send back to the
client. Lazy fetching will not work across the client / server
boundary, so you must ensure that your code fetches all relations
eagerly (via an annotation or a separate call if needed).
2. JDO and JPA implementations use proxy classes for objects attached
to a persistence manager. Before they can be sent back to the client,
you must detach all objects from the PM.
3. Even then, GWT won't be able to serialize any types for which it
doesn't know the source (like App Engine's Key class). The open source
Gilead project and others like Objectify provide GWT wrappers for
these.
HTH,
/dmc
On Mon, Nov 8, 2010 at 8:17 PM, dparish dpar...@gmail.com wrote:
I have an entity with a member like this:
@Entity
public class Foo implements Serializable{
�...@onetomany(mappedBy=foo,targetEntity=InternalText.class,
fetch=FetchType.EAGER) // I tried Lazy too.
private ArrayListInternalTextinternalTextEntries;
When I try to use Foo I get this error:
Throwable occurred:
com.google.gwt.user.client.rpc.SerializationException: Type
'org.apache.openjpa.util.java$util$ArrayList$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy or its Class object could not be loaded. For
security purposes, this type will not be serialized.: instance =
[blah.blah.entities.internalt...@36ae36ae,
blah.bhla.entities.internalt...@3fca3fca,
blah.blah.retain.entities.internalt...@42474247,
blah.blah.entities.internalt...@48724872]
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
ze(ServerSerializationStreamWriter.java:
610)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.write
Object(AbstractSerializationStreamWriter.java:
129)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
zeValue(ServerSerializationStreamWriter.java:
534)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
zeClass(ServerSerializationStreamWriter.java:
700)
From what I can tell openjpa is creating a helper representation of
ArrayList that it uses to assist in monitoring and lazy loading the
child table. I've tried eager and lazy fetching.
I tried this:
ArrayListInternalText newText = new ArrayListInternalText();
for (InternalText textItem: foo.getInternalTextEntries()) {
newText.add(textItem);
}
foo.setInternalTextEntries(newText);
It got past my error, but then the next layer down had trouble (Date
in the InternalText class)
Type 'org.apache.openjpa.util.java$util$Date$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://groups.google.com/group/google-web-toolkit?hl=en.
--
David Chandler
Developer Programs Engineer, Google Web
Toolkithttp://googlewebtoolkit.blogspot.com/
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: OpenJPA GWT serialization problem.
Thanks David.
I tried LAZY and EAGER. Both caused the problem.
For #2, that seems promising. There's an EntityManager clear method,
but that would affect all threads using the entity manager. Any
thoughts on how to do that detach?
On Nov 8, 8:20 pm, David Chandler drfibona...@google.com wrote:
Hi dparish,
There are three issues here:
1. GWT needs a fully populated object graph to send back to the
client. Lazy fetching will not work across the client / server
boundary, so you must ensure that your code fetches all relations
eagerly (via an annotation or a separate call if needed).
2. JDO and JPA implementations use proxy classes for objects attached
to a persistence manager. Before they can be sent back to the client,
you must detach all objects from the PM.
3. Even then, GWT won't be able to serialize any types for which it
doesn't know the source (like App Engine's Key class). The open source
Gilead project and others like Objectify provide GWT wrappers for
these.
HTH,
/dmc
On Mon, Nov 8, 2010 at 8:17 PM, dparish dpar...@gmail.com wrote:
I have an entity with a member like this:
@Entity
public class Foo implements Serializable{
�...@onetomany(mappedBy=foo,targetEntity=InternalText.class,
fetch=FetchType.EAGER) // I tried Lazy too.
private ArrayListInternalTextinternalTextEntries;
When I try to use Foo I get this error:
Throwable occurred:
com.google.gwt.user.client.rpc.SerializationException: Type
'org.apache.openjpa.util.java$util$ArrayList$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy or its Class object could not be loaded. For
security purposes, this type will not be serialized.: instance =
[blah.blah.entities.internalt...@36ae36ae,
blah.bhla.entities.internalt...@3fca3fca,
blah.blah.retain.entities.internalt...@42474247,
blah.blah.entities.internalt...@48724872]
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
ze(ServerSerializationStreamWriter.java:
610)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.write
Object(AbstractSerializationStreamWriter.java:
129)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
zeValue(ServerSerializationStreamWriter.java:
534)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
zeClass(ServerSerializationStreamWriter.java:
700)
From what I can tell openjpa is creating a helper representation of
ArrayList that it uses to assist in monitoring and lazy loading the
child table. I've tried eager and lazy fetching.
I tried this:
ArrayListInternalText newText = new ArrayListInternalText();
for (InternalText textItem: foo.getInternalTextEntries()) {
newText.add(textItem);
}
foo.setInternalTextEntries(newText);
It got past my error, but then the next layer down had trouble (Date
in the InternalText class)
Type 'org.apache.openjpa.util.java$util$Date$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://groups.google.com/group/google-web-toolkit?hl=en.
--
David Chandler
Developer Programs Engineer, Google Web
Toolkithttp://googlewebtoolkit.blogspot.com/
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: OpenJPA GWT serialization problem.
In JDO, there are pm.detachX() methods you can use to do this. In JPA,
it appears detachment is automatically done via an annotation, but the
detached objects will still contain non-serializable stuff. Details
here:
http://timepedia.blogspot.com/2009/04/google-appengine-and-gwt-now-marriage.html
HTH,
/dmc
On Tue, Nov 9, 2010 at 7:59 AM, dparish dpar...@gmail.com wrote:
Thanks David.
I tried LAZY and EAGER. Both caused the problem.
For #2, that seems promising. There's an EntityManager clear method,
but that would affect all threads using the entity manager. Any
thoughts on how to do that detach?
On Nov 8, 8:20 pm, David Chandler drfibona...@google.com wrote:
Hi dparish,
There are three issues here:
1. GWT needs a fully populated object graph to send back to the
client. Lazy fetching will not work across the client / server
boundary, so you must ensure that your code fetches all relations
eagerly (via an annotation or a separate call if needed).
2. JDO and JPA implementations use proxy classes for objects attached
to a persistence manager. Before they can be sent back to the client,
you must detach all objects from the PM.
3. Even then, GWT won't be able to serialize any types for which it
doesn't know the source (like App Engine's Key class). The open source
Gilead project and others like Objectify provide GWT wrappers for
these.
HTH,
/dmc
On Mon, Nov 8, 2010 at 8:17 PM, dparish dpar...@gmail.com wrote:
I have an entity with a member like this:
@Entity
public class Foo implements Serializable{
�...@onetomany(mappedBy=foo,targetEntity=InternalText.class,
fetch=FetchType.EAGER) // I tried Lazy too.
private ArrayListInternalTextinternalTextEntries;
When I try to use Foo I get this error:
Throwable occurred:
com.google.gwt.user.client.rpc.SerializationException: Type
'org.apache.openjpa.util.java$util$ArrayList$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy or its Class object could not be loaded. For
security purposes, this type will not be serialized.: instance =
[blah.blah.entities.internalt...@36ae36ae,
blah.bhla.entities.internalt...@3fca3fca,
blah.blah.retain.entities.internalt...@42474247,
blah.blah.entities.internalt...@48724872]
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
ze(ServerSerializationStreamWriter.java:
610)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.write
Object(AbstractSerializationStreamWriter.java:
129)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
zeValue(ServerSerializationStreamWriter.java:
534)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.seriali
zeClass(ServerSerializationStreamWriter.java:
700)
From what I can tell openjpa is creating a helper representation of
ArrayList that it uses to assist in monitoring and lazy loading the
child table. I've tried eager and lazy fetching.
I tried this:
ArrayListInternalText newText = new ArrayListInternalText();
for (InternalText textItem: foo.getInternalTextEntries()) {
newText.add(textItem);
}
foo.setInternalTextEntries(newText);
It got past my error, but then the next layer down had trouble (Date
in the InternalText class)
Type 'org.apache.openjpa.util.java$util$Date$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://groups.google.com/group/google-web-toolkit?hl=en.
--
David Chandler
Developer Programs Engineer, Google Web
Toolkithttp://googlewebtoolkit.blogspot.com/
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
David Chandler
Developer Programs Engineer, Google Web Toolkit
http://googlewebtoolkit.blogspot.com/
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
OpenJPA GWT serialization problem.
I have an entity with a member like this:
@Entity
public class Foo implements Serializable{
@OneToMany(mappedBy=foo,targetEntity=InternalText.class,
fetch=FetchType.EAGER) // I tried Lazy too.
private ArrayListInternalTextinternalTextEntries;
When I try to use Foo I get this error:
Throwable occurred:
com.google.gwt.user.client.rpc.SerializationException: Type
'org.apache.openjpa.util.java$util$ArrayList$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy or its Class object could not be loaded. For
security purposes, this type will not be serialized.: instance =
[blah.blah.entities.internalt...@36ae36ae,
blah.bhla.entities.internalt...@3fca3fca,
blah.blah.retain.entities.internalt...@42474247,
blah.blah.entities.internalt...@48724872]
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:
610)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:
129)
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:
534)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeClass(ServerSerializationStreamWriter.java:
700)
From what I can tell openjpa is creating a helper representation of
ArrayList that it uses to assist in monitoring and lazy loading the
child table. I've tried eager and lazy fetching.
I tried this:
ArrayListInternalText newText = new ArrayListInternalText();
for (InternalText textItem: foo.getInternalTextEntries()) {
newText.add(textItem);
}
foo.setInternalTextEntries(newText);
It got past my error, but then the next layer down had trouble (Date
in the InternalText class)
Type 'org.apache.openjpa.util.java$util$Date$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: OpenJPA GWT serialization problem.
Hi dparish,
There are three issues here:
1. GWT needs a fully populated object graph to send back to the
client. Lazy fetching will not work across the client / server
boundary, so you must ensure that your code fetches all relations
eagerly (via an annotation or a separate call if needed).
2. JDO and JPA implementations use proxy classes for objects attached
to a persistence manager. Before they can be sent back to the client,
you must detach all objects from the PM.
3. Even then, GWT won't be able to serialize any types for which it
doesn't know the source (like App Engine's Key class). The open source
Gilead project and others like Objectify provide GWT wrappers for
these.
HTH,
/dmc
On Mon, Nov 8, 2010 at 8:17 PM, dparish dpar...@gmail.com wrote:
I have an entity with a member like this:
@Entity
public class Foo implements Serializable{
�...@onetomany(mappedBy=foo,targetEntity=InternalText.class,
fetch=FetchType.EAGER) // I tried Lazy too.
private ArrayListInternalTextinternalTextEntries;
When I try to use Foo I get this error:
Throwable occurred:
com.google.gwt.user.client.rpc.SerializationException: Type
'org.apache.openjpa.util.java$util$ArrayList$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy or its Class object could not be loaded. For
security purposes, this type will not be serialized.: instance =
[blah.blah.entities.internalt...@36ae36ae,
blah.bhla.entities.internalt...@3fca3fca,
blah.blah.retain.entities.internalt...@42474247,
blah.blah.entities.internalt...@48724872]
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:
610)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:
129)
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:
534)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeClass(ServerSerializationStreamWriter.java:
700)
From what I can tell openjpa is creating a helper representation of
ArrayList that it uses to assist in monitoring and lazy loading the
child table. I've tried eager and lazy fetching.
I tried this:
ArrayListInternalText newText = new ArrayListInternalText();
for (InternalText textItem: foo.getInternalTextEntries()) {
newText.add(textItem);
}
foo.setInternalTextEntries(newText);
It got past my error, but then the next layer down had trouble (Date
in the InternalText class)
Type 'org.apache.openjpa.util.java$util$Date$proxy' was not included
in the set of types which can be serialized by this
SerializationPolicy
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
David Chandler
Developer Programs Engineer, Google Web Toolkit
http://googlewebtoolkit.blogspot.com/
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Serialization problem !!!!
Hi olivier, Thanks a lot for prompt reply, The solution you said works fine if we extend our class from RemoteServiceServlet . However in my case I am not extending the class from RemoteServiceServlet . I am making the use of HandlerAdapter class of spring for integrating spring wid GWT. Is there any way to achive the same kinda functionality there by not extending from RemoteServiceSerlvet class. Thanks Samir --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: GWT Serialization problem !!!!
Hi olivier, Thanks a lot for prompt reply, The solution you said works fine if we extend our class from RemoteServiceServlet . However in my case I am not extending the class from RemoteServiceServlet . I am making the use of HandlerAdapter class of spring for integrating spring wid GWT. Is there any way to achive the same kinda functionality there by not extending from RemoteServiceSerlvet class. Thanks Samir --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: GWT Serialization problem !!!!
Hi sam, I had the same issue while integrating with acegi, what I choose was to extract the code of RemoteServiceServlet in a helper On Fri, Oct 17, 2008 at 8:40 AM, Sam [EMAIL PROTECTED] wrote: Hi olivier, Thanks a lot for prompt reply, The solution you said works fine if we extend our class from RemoteServiceServlet . However in my case I am not extending the class from RemoteServiceServlet . I am making the use of HandlerAdapter class of spring for integrating spring wid GWT. Is there any way to achive the same kinda functionality there by not extending from RemoteServiceSerlvet class. Thanks Samir -- Si l'ignorance peut servir de consolation, elle n'en est pas moins illusoire. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: GWT Serialization problem !!!!
Can you please share that code to me ? That will be a great help !! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: GWT Serialization problem !!!!
Hi You should call : RPC.decodeRequest(payload,this.remoteServiceClass, *this*); *this* being the remote servlet (SerializationPoliciyProvider) To resolve the serialization policy (That allow the GWT serialization of Serializable). If no SerializationPoliciyProvider or his the resolution fails to DefaultPolicies (GWT 1.3) is applied and Object must be IsSerializable. You can look at: http://code.google.com/p/net-orcades-spring/source/browse/trunk/orcades-spring-gwt/src/main/java/net/orcades/spring/gwt/SpringGWTRemoteServlet.java from my Spring integration: http://code.google.com/p/net-orcades-spring/ hih On Wed, Oct 15, 2008 at 4:17 PM, Sam [EMAIL PROTECTED] wrote: Hello all, I have written a code which will integrate the GWT with spring . For this purpose I have overridden the public String processCall(String payload) methode. This works fine if any class which needs to be serilized is implementing isSerilizabel interface. However if I implement the serilizabel interface insted of isSerilizabel , I get serilization exception. Error occours when I try to decode the request by using following code. RPCRequest rpcRequest = RPC.decodeRequest(payload,this.remoteServiceClass); Is there any way by which my code will run there by implementing Serilizabel interface ONLY. Any white paper , any link will greatly be appriciated. Thanks, Samir -- Si l'ignorance peut servir de consolation, elle n'en est pas moins illusoire. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: GWT Serialization problem !!!!
Sorry for my poor expression... If no SerializationPoliciyProvider is given (your case) or if the resolution fails GWT DefaultPolicies (GWT 1.3) is applied and Object must be IsSerializable. On Wed, Oct 15, 2008 at 4:54 PM, olivier nouguier [EMAIL PROTECTED] wrote: Hi You should call : RPC.decodeRequest(payload,this.remoteServiceClass, *this*); *this* being the remote servlet (SerializationPoliciyProvider) To resolve the serialization policy (That allow the GWT serialization of Serializable). If no SerializationPoliciyProvider or his the resolution fails to DefaultPolicies (GWT 1.3) is applied and Object must be IsSerializable. You can look at: http://code.google.com/p/net-orcades-spring/source/browse/trunk/orcades-spring-gwt/src/main/java/net/orcades/spring/gwt/SpringGWTRemoteServlet.java from my Spring integration: http://code.google.com/p/net-orcades-spring/ hih On Wed, Oct 15, 2008 at 4:17 PM, Sam [EMAIL PROTECTED] wrote: Hello all, I have written a code which will integrate the GWT with spring . For this purpose I have overridden the public String processCall(String payload) methode. This works fine if any class which needs to be serilized is implementing isSerilizabel interface. However if I implement the serilizabel interface insted of isSerilizabel , I get serilization exception. Error occours when I try to decode the request by using following code. RPCRequest rpcRequest = RPC.decodeRequest(payload,this.remoteServiceClass); Is there any way by which my code will run there by implementing Serilizabel interface ONLY. Any white paper , any link will greatly be appriciated. Thanks, Samir -- Si l'ignorance peut servir de consolation, elle n'en est pas moins illusoire. -- Si l'ignorance peut servir de consolation, elle n'en est pas moins illusoire. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~--~~~~--~~--~--~---
