Hi Ryan,
The proxy you get from RequestContext.create() won't be updated
automatically. Your persist method should return the newly persisted object
from the server.
Does that help?
/dmc
On Thu, Jun 23, 2011 at 8:51 PM, Ryan McFall mcfall.r...@gmail.com wrote:
Thanks David, for confirming my
David:
Yep, I thought of that, and have implemented it. It seems to work
well. Thanks for your help!
Ryan
On Jun 24, 9:32 am, David Chandler drfibona...@google.com wrote:
Hi Ryan,
The proxy you get from RequestContext.create() won't be updated
automatically. Your persist method should
If I have an Request object and I call create to generate a new proxy
instance, when, if ever, will my constructor for the class that is
being proxied be called? It seems this is the purpose of the create
method in the Locator class, but I don't see that method being
called. I guess I'm not
The purpose of the create method is to associate a request context with the
newly created object. It has to be done through the RequestContext so that
it can be managed and all the goodies that come with request factory can be
enforced.
--
You received this message because you are subscribed
Are you referring to the create method on the client (in my
RequestContext sublcass), or the create method in the Locator (which I
believe would be run on the server)?
I think you're referring to the client-side create method; my question
about create is mostly what the server-side version is
Ryan, you're correct. Nothing on the server gets called until you fire() the
request, so your default properties won't be immediately available on the
client, unfortunately.
On Thu, Jun 23, 2011 at 3:44 PM, Ryan McFall mcfall.r...@gmail.com wrote:
Are you referring to the create method on the
Thanks David, for confirming my suspicions.
I've got this working now so that immediately after I
RequestContext.create my proxy, I call a method on the server to
persist it.
In side that server method, I refresh the state of the object after
saving it, because a database trigger populates some
