Have a look at AbstractRequestContext (particularly the 
processReturnOperations method; also look for calls to setTag), but 
basically you'll have to transport more than the AutoBean data: you'll have 
to send its stableId and version (have a look at SimpleRequestContext et 
al. for how they're computed).
You'll also have to apply the BaseProxycategory, EntityProxyCategory and 
ValueProxyCategory to your AutoBeanFactory, and @NoWrap the EntityProxyId. 
Have a look at the RequestFactoryGenerator or run the DevMode or Compiler 
with the -gen argument to look at what's generated.

All in all, it might be better (and I really mean *might*, as I have not 
actually looked at it in details) to use a ProxySerializer or extend the 
AbstractRequestContext to use RF's serialization.

Search the group, there has been a similar question in the past months (and 
I made basically the same answer).

On Thursday, March 29, 2012 12:10:09 PM UTC+2, Eugene Ivlev wrote:
>
> I have such problem: 
>
> I use RF as main CRUD client-server interface, but I also use 
> Atmosphere framework as server-push mechanism. 
> My aim is multi-client application. All clients must receive 
> notification about changes made by anyone.  The communication looks 
> like this: 
>
>
> @ProxyFor(TestEntity.class) 
> TestProxy extends EntityProxy 
>
>
>
>                         |                                | 
>           TestProxy obj        |--------RF update entity------>|--- 
>  RequestFactory 
> Servlet 
>                         |                                |  | 
>                         |                                |  | 
>                         |                                |  | 
>                         |                                |  | 
> AutoBean<TestProxy> obj        |<--Atmosphere notification-----|<-| 
> Atmosphere Servlet creates AutoBean<TestProxy> 
>                         |   with entity to all client        | 
>                         |                                | 
>                         |                                | 
>                         |                                | 
>                         |                                | 
>                         |                                | 
>                         |                                | 
>                         client                                 server 
>
> But RF adds to AutoBean some kind of additional information. Therefore 
> I can't use autobaen received from Atmosphere in next communication by 
> RF channel. 
> How I can create autobean as RF does it?

-- 
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/-/XoGFX3xfzGYJ.
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.

Reply via email to