Group items tagged

> Does anybody have an idea for a nasty workaround for that problem that > is possible with the current GWT 2.1 implementation? One that I wouldn't call "nasty": 1. extend DefaultRequestTransport to send the uniqueCustomerName (say, within an HTTP header) 2. initialize() your RequestFactory with an instance of your extended RequestTransport 3. on the server-side, get the HttpServletRequest using RequestFactoryServlet.getThreadLocalRequest(), to extract the uniqueCustomerName from it and use it to create the EntityManagerFactory. That way, you don't have to send the uniqueCustomerName explicitly in each and every request, it'll be done automatically and transparently by your RequestTransport.

GWT 2.1 has introduced new framework: RequestFactory for working with server object (entity or not entity) more easily. According to Google, GWT-RequestFactory is data-oriented and GWT-RPC is service-oriented. In my opinion, GWT-RequestFactory works like lightweight remoting-object mechanism with 2 hands; in otherwise, traditional GWT-RPC works like remoting-method mechanism. The 2 hands of GWT-RequestFactory are EntityProxy and RequestContext: -EntityProxy: remotes getters/setters of server object -RequestContext: remotes methods of server object With RequestFactory, developers can build their app more data-oriented and more object-oriented. Below is an example for building a simple app by using GWT-RequestFactory in MVP framework.