requestfactory

I'm new to RequestFactory but with generous help of Thomas Broyer and after reviewing documents below it's getting much better :) Getting Started with RequestFactory Request Factory Moving Parts RequestFactory changes in GWT 2.4 But could you please explain why Locator<>.find() is being called so unnecessarily (in my opinion) often ? In my sample project I have two entities Organization and Person that maintain parent-child relationship. When I fetch Organization Objectify automatically fetches child Person. Also I created two methods in my service layer findOrganizationById and

Background I am in the middle of developing a web application using GWT, Java, and EclipseLink. Each of those selections are choices I have made to implement this program. GWT is the only choice where there is not a firm grasp as to what it is exactly compared to something like Spring. Right now I use GWT widgets to implement the client and GWT RequestFactory to implement the server-client communication of entities from EclipseLink. Views So I view GWT as primarily a library of widgets with a simple framework for server-client communication. This is much the same way I view Spring, a library

I am trying to use RequestFactory. My ORM provider is JPA. I have a method to retrieve a list of entity called findAll(). When the user requests for a list of entities, findAll is called. Find all executes a query against database and returns a list of entities. However, when requestFactory is asked to send this list back to the user, requestfactory calls findEntity() for each entity in the list. My question is: is there any way I can instruct request factory to not call find entity for each item in the list? This is likely from SimpleRequestProcessor.createReturnOperations() determining

I'm using GWT and RequestFactory on a new project that needs authentication. Where would be the best place to add the login and logout functions ? in a UserRequestContext ? Thanks in advance. Use servlet filter. I split RequestFactory calls into two streams - one for unauthenticated calls and another one for authenticated ones. Here is piece of my web.xml . <servlet> <servlet-name>CustomRequestFactoryServlet</servlet-name> <servlet-class>my.server.CustomRequestFactoryServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>CustomRequestFactoryServlet</servlet-name> <url-pattern>

I´m using GWT 2.4 and Spring 3.1 and I want to secure my application with Spring Security . I was looking for a GWT-only solution without a separate JSP login page. I found only old sites using JSP to do login, so this thread could result in a solution to fully integrate GWT with Spring Security in a standard way. Anyway, if there is a reference where this has been done successfully already, this thread can be closed with a link to that reference of course. So far here is my first approach: applicationcontext-security.xml: <http auto-config="false" use-expressions="true" entry-point-ref=

I am trying to figure out if I should migrate my gwt-rpc calls to the new GWT2.1 RequestFactory cals. Google documentation vaguely mentions that RequestFactory is a better client-server communication method for "data-oriented services" What I can distill from the documentation is that there is a new Proxy class that simplifies the communication (you don't pass back and forth the actual entity but just the proxy, so it is lighter weight and easier to manage) Is that the whole point or am I missing something else in the big picture? The big difference between GWT RPC and RequestFactory is that