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.
