Thanks, Thomas. I tried to override isLive in the service decorator,
but creating a locator will be a more effective strategy.
On Mar 10, 2:47 pm, Thomas Broyer t.bro...@gmail.com wrote:
This is the default implementation for isLive, so RequestFactory can
detect if an object has been deleted
Hi there! Hoping for some insight on this one. I have an Entity that
returns a list of related entities.
@Entity
class MyEntity {
private relatedList;
public static ListRelatedEntity getRelatedEntities() { return
relatedList; }
}
I eagerly fetch these related items myself on the server
Oh, and that get method is instance, not static. Loaded on the lookup
for MyEntity.
Thanks!
--
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
I've seen this as well. My suspicion based on some debugging and breakpoint
work is that the RequestFactory is properly retrieving the related objects
using the relation, but then immediately querying them all again to verify
their version numbers match the ones from the DB.
I worked around
This is the default implementation for isLive, so RequestFactory can
detect if an object has been deleted (and then dispatch an
EntityProxyChange(DELETED) event).
You can override it in your Locator if you have one.
--
You received this message because you are subscribed to the Google Groups
