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
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
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:
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
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:
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
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
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.
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
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
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
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
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
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 :
14 matches
Mail list logo
