Re: GWT 2.1.1 and DAOs

2010-12-21 Thread Sebastian
Further investigation has revealed that SimpleRequestProcessor call's ServiceLayer#isLive() for every non-null domain object to check if it's still there. Otherwise the write operation is set to DELETE. IMO that's terrible: I don't want to do two entity manager/db lookups for every find (even if

Re: GWT 2.1.1 and DAOs

2010-12-21 Thread Thomas Broyer
On Tuesday, December 21, 2010 1:25:18 PM UTC+1, Sebastian wrote: Further investigation has revealed that SimpleRequestProcessor call's ServiceLayer#isLive() for every non-null domain object to check if it's still there. Otherwise the write operation is set to DELETE. IMO that's terrible:

GWT 2.1.1 and DAOs

2010-12-19 Thread Henrik Schmidt
Hi there, I'm playing with the new 2.1.1 release. I'm trying to use DAOs instead of DTOs and testing it through RequestFactoryMagic. I use Guice server side to inject the DAOs and I've implemented a ServiceLocator to hook into Guice and get the given instance. This seems to work well. Here's the

Re: GWT 2.1.1 and DAOs

2010-12-19 Thread Henrik Schmidt
I had a look through the code. com.google.gwt.requestfactory.server.RequestFactoryInterfaceValidator has a (rather unfortunately named) method called checkIdAndVersion(ErrorContext logger, Type domainType) in line 1001. However, this method also checks for a find method. Is this a bug? In other

Re: GWT 2.1.1 and DAOs

2010-12-19 Thread Thomas Broyer
The findXxx method is required when de-serializing instances. If you can't or don't one that static method, then you have to use a Locator. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to