Hallo, I would like to use RequestFactory mechanism as a way for retrival of data from server. I have looked at the RequestFactory overwiev as well as the expenses example and I have came up with some questions which bother me..
I have already working project where I have DAO classes on the server side, and entity(domain) classes also on the server side (previously I've used Gilead to send entities to the client). My entities are pure domain classes without any business logic and I would like to follow this pattern. 1) What I see in the google expenses example is that the Enitity class is holding not only data model but also business logic, also as far as I've understood any Entity must have findEntity( Long|String id) , which is business method. -Why it is designed like this? Is this the correct way to design application to put data model and business logic together? Can I put it separately? 2) I have tried to use my DAO classes as parameter for RequestContext class like @Service(MyEntityDao.class) public interface EntityRequest extends RequestContext I have also problems with persist() and remove() methods which should return InstanceRequest<EntityProxy, eventual_return_type> persist(); when implemented those methods in my dao I have gw-compiler error: [ERROR] Parameter 0 of method EntityRequest.persist does not match methodMyEntityDao.persist -Are those methods allowed outside Etnity class? can I implement them in my Dao classes? Thanks in advance for any responce:) greetings, agi -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
