Objectify runs fairly close to the datastore (ie if you understand the
datastore, you won't be irritated by high-level abstractions) and it's
dead-easy to take advantage of caching. I wouldn't even think about it,
personally - I'd just use Objectify. For you, it's a small investment to
try it
On Tuesday, December 6, 2011 10:20:58 PM UTC+1, David Chandler wrote:
Objectify works great with RequestFactory:
Indeed! I'm already using RequestFactory (partly with the ServiceLocator
pattern) and JPA2 at my company's project.
Thanks to your
On Wednesday, December 7, 2011 7:51:53 AM UTC+1, ra wrote:
On Tue, Dec 6, 2011 at 10:20 PM, David Chandler drfib...@google.com
wrote:
Objectify works great with RequestFactory:
http://code.google.com/p/listwidget/
Do you have a specific concern about it?
Btw - JPA2 and Objectify
*Is there a good/better alternative to Objectify?* I want to use a
Datastore abstraction layer like JPA2 together with GWT's RequestFactory
using its ServiceLocator pattern. Is the usage of Objectify
even advisable in this case or should I use the Datastore directly (which
I've done 2y ago...
Objectify works great with RequestFactory:
http://code.google.com/p/listwidget/
Do you have a specific concern about it?
/dmc
On Tue, Dec 6, 2011 at 2:51 AM, Alexander Orlov
alexander.or...@loxal.netwrote:
*Is there a good/better alternative to Objectify?* I want to use a
Datastore
On Tue, Dec 6, 2011 at 10:20 PM, David Chandler drfibona...@google.com wrote:
Objectify works great with RequestFactory:
http://code.google.com/p/listwidget/
Do you have a specific concern about it?
Btw - JPA2 and Objectify are similar in terms of technology. So you
can always use
