thanks, btw, is there any problem that a service will contain it's own
locator?
what i've done is uinify the Service and Entity Locator into one class
(where you have a generic Entity locator which implements the finder
methods and then a service locator which extends it with the new Instance
i know this has been asked before, but i'm not sure how to respond to
it.
given that requestContext and it's implementation parallal the Dao's
of jpa, it's plausible to create a generic dao with entity methods
like persist
so i thought i would create a generic interface like
CommonRequestContext
Server-side inheritance of RequestFactory services with generics works
fine. See
http://turbomanage.wordpress.com/2011/03/25/using-gwt-requestfactory-with-objectify/
Client-side inheritance of RequestContext interfaces is coming in 2.4. See
