The editor framework can give you the info for the with calls, but it's up
to you to use it. If you want everything, put the contents of
RequestFactoryEditorDriver.getPaths() into your with() call.
On Sun, Oct 3, 2010 at 4:10 PM, Ray Cromwell <cromwell...@gmail.com> wrote:
>
> Any relational (non-value fields) are by default not sent back with a
> request, you must request them with the with() method, e.g.
> with("superVisor"). Just because you sent some object over with that field,
> doesn't mean that the field will also be returned to you, because a method
> could potentially return a very large set of objects, e.g.
>
> Request<List<EmployeeProxy>> getEmployeesFrom(EmployeeProxy boss);
>
> Here I am passing the manager's proxy, and it might have a
> Collection<EmployeeProxy> managedEmployees on it, but if I'm only interested
> in the names of the people that 'boss' manages, I don't want to
> automatically return the 'managedEmployees' field of each returned object,
> even if it was present on boss, so instead, you write
>
> getEmployeesFrom(boss).with("managedEmployees").fire(...) if you want that
> field.
>
> Perhaps the editor framework is not setting up these with() calls as it
> should be?
>
> On Sun, Oct 3, 2010 at 3:11 PM, Patrick Julien <pjul...@gmail.com> wrote:
>
>> I'm getting used to this editor framework and I like it a lot,
>> unfortunately, I think I've stumble upon a blocker for me.
>>
>> EntityProxy's that contain collections are not being filled in. So
>> you can send up an object graph in one shot in order to save it.
>> Which is great.
>>
>> Unfortunately, on return, the object graph only contains the root.
>> This is because in JsoRequestProcessor.requestedProperty, it does:
>>
>> if (EntityProxy.class.isAssignableFrom(leafType)) {
>> return propertyContext.hasProperty(p.getName());
>> }
>>
>> to check if child entities should be included but that's an empty set
>> so it always returns false
>>
>> If it wasn't, we have TODO here TODO: use the properties
>> * that should be coming with the request.
>>
>> that says this thing should eventually be able to do this but wouldn't
>> the safest behavior for now to include all the contents of the Entity
>> that are featured in EntityProxyId? I'm stuck at this point.
>>
>> --
>> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
