Thank you, it all makes sense now. However what you described is how GWT RF uses those details to do its magic behind the scenes.
I am not clear what our responsibility is then ? What should go inside the Locator ? >From the code I posted, http://paste.pocoo.org/show/308153/ I don't know what I should put in there. I have a ServiceLocator ( one per application), that locates Services. those Services are independent from GWT RF, they can connect to persistent stores, do whatever they want. and return a retult/perform action that is expected by RequestContext. and what you described for Locators @ProxyFor(value=PersonEntity, locator=EntityLocator) public interface PersonProxy { from your explanation I understood why Locator is important, but what should we/the developers put in it ? and do we need one per Entity or one per Application ? sorry I repeated myself, I am still a bit confused :" ) -- 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.
