The specification is the code ;-) Have a look at the com.google.web.bindery.requestfactory.shared.messages.* classes for the payload data, and the AbstractRequestContext and SimpleRequestProcessor for how their semantics. In the ResponseMessage, there will either be general failure (causes onFailure to be called on all Receivers, including most importantly the "global" one, optionally passed to the fire() method of the RequestContext), violations (same as a general failure, but onConstraintViolations will be called instead of onFailure) or all three of operations, status codes and invocation results (actually, status codes and invocation results go by pair, and either one of operations or status-codes/invocation-results could be empty, but I don't think they could both be). Operations are data about proxies (have they been created/updated/deleted, along with their properties, as requested by the with() on the Requests); status codes gives the result/failure status of each method invocation (will trigger either onSuccess or onFailure of the Receiver associated with the method invocation) and invocation results (paired to the status codes by their index in the lists) will be either a ServiceFailureMessage (passed on onFailure) or the result (passed to onSuccess), depending on the status code.
On Monday, March 26, 2012 10:11:20 PM UTC+2, Miroslav Genov wrote: > > Hello, > > Does anyone knows where there is a specification of the wire format which > RF is using by default ? > > Regards, > Miroslav > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/-n6d-DcrTDoJ. 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.
