Hi Thomas, I understand that. It is just that I thought that the whole thing of having a ServiceLocator was a way of getting rid of the entity manager dependency in my entity. I have my entity manager in my DAO, my Service Bean knows my DAO.
As far as I understood, I can either setup a ServiceLocator or a Locator, or can I have both? And why should I? brgds, Papick On 22 Feb., 11:25, Thomas Broyer <[email protected]> wrote: > You need a Locator for the POIEntity. > > When sending an entity from client to server, you actually just send its ID > and the modified properties. On the server side, the object is first > retrieved from your datastore using its ID (using its static findPOIEntity > method, or the Locator's find method), then setters are called for each > modified property (and then the entity is passed to your service method, and > only then the ServiceLocator will be used, if needed) -- 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.
