gwtrequestfactory

Requestfactory clone proxy to new context


I'm facing the gwt issue 5794 : http://code.google.com/p/google-web-toolkit/issues/detail?id=5794

I have seen there is a 8 month old patch for it but it has not been included in gwt 2.5 RC1 http://gwt-code-reviews.appspot.com/1620804/

Does anyone know if this patch will be included in gwt 2.5 rc2 or final release ?

if not, could someone please explain me what would be the best workaround for that problem.

Thanks in advance.


Solution

  • It won't.

    From the first review (which happens to be by myself):

    In brief: this patch is not enough, it breaks a lot of rules ("crossed streams"), and the test is broken.

    In case you cannot use the serialize/deserialize workaround suggested in the issue, I believe there's a way to clone things using an AutoBeanVisitor.

    The current "only one RequestContext can edit a given proxy –identified by its stableId– at a given time" is really annoying, and not really justified (no longer at least; it was in early iterations of Request Factory). This is something I'd like to get rid of in the future, but we have some other big things to do first.