You could add the with("address") to the findAll call:
requestFactory.personRequest().findAll().with("address").fire(...);
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegrou
> AFAICT, actually, when doing your second request
> (find(personId).with("address")), the previous entity proxy will be
> updated; i.e. for each proxy there's a "canonical", immutable instance
> that's being updated in place when a response comes back from the
> server, and there are "editable"
On 25 oct, 20:50, Rafi wrote:
> On 25 Paź, 20:29, Thomas Broyer wrote:
>
> > """
> > When querying the server, RequestFactory does not automatically
> > populate relations in the object graph. To do this, use the with()
> > method on a request and specify the related property name as a String:
On 25 Paź, 20:29, Thomas Broyer wrote:
> """
> When querying the server, RequestFactory does not automatically
> populate relations in the object graph. To do this, use the with()
> method on a request and specify the related property name as a String:
>
> Request findReq =
> requestFactory.per
On 25 oct, 13:14, Rafi wrote:
> Hi!
>
> I am playing around with new RequestFactory feature available in 2.1,
> and actually I think that I don't get the idea.
>
> At first i thought, that RequestFactory will bring me something like
> local domain model.
> Lets assume that entity A and proxy for
Hi!
I am playing around with new RequestFactory feature available in 2.1,
and actually I think that I don't get the idea.
At first i thought, that RequestFactory will bring me something like
local domain model.
Lets assume that entity A and proxy for it are present. Lets assume
that this entity A
