Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Why are you trying to serialize RF messages and send them just as entities? RequestFactory is much more than justa way to send data over the wire - it has at least three different kinds of messages that can be sent from the client to the server: create instances, call setters, and invoke service methods. Based on what happens on the server, not only can data be returned to the client, but messages about what changes were made and if those setters made changes that are not valid under the JSR303 rules.</p> <p>Are you trying for a simpler, interface way of describing, sending, and receiving entities? Or do you actually want the RF wiring on both client and server so you can batch requests, refer to EntityProxyId instances and have the client only send diffs?</p> <p>If you just want simpler object declarations, try just using <code>AutoBean</code>s and the <code>AutoBeadCodex</code> you have already looked at - you'll be able to create and marshal instances on both client and server easily, and you can pass them as strings over atmosphere's transports.</p> <p>If you actually want RequestFactory, but running over something other than AJAX, there are other options. Rather than sending/receiving strings through Atmosphere (which I believe is intended to provide push support for RPC calls), consider using that underlying push layer to implment a new request transport in RequestFactory.</p> <p><code>com.google.web.bindery.requestfactory.shared.RequestTransport</code> can be implemented (see <code>com.google.web.bindery.requestfactory.gwt.client.DefaultRequestTransport</code> for the default AJAX version) to use any communication mechanism you would like - and to build the server, take a look at <code>com.google.web.bindery.requestfactory.server.RequestFactoryServlet</code> for what actually must be done to push messages through the Locator, ServiceLocators, etc. </p> <p>If you really want to use Atmosphere and RF, then consider building a <code>RequestTransport</code> that wraps a simple Atmosphere interface to call to the server with the string - the cometd/websocket calls will already be taken care of for you, and you'll just have to translate the string message into invocations (again, see how RequestFactoryServlet does it).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload