On Wed, Oct 20, 2010 at 12:02 PM, BobV wrote:
> On Wed, Oct 20, 2010 at 11:34 AM, Tim Murison wrote:
>> Any updates on this issue?
>
> I am burning down the server code this week.
Will it be replaced with some shiny new server code?
--
http://groups.google.com/group/Google-Web-Toolkit-Contribu
On Wed, Oct 20, 2010 at 11:34 AM, Tim Murison wrote:
> Any updates on this issue?
I am burning down the server code this week.
--
Bob Vawter
Google Web Toolkit Team
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
More notes on this:
Say I have the following relationship, a User has a list of
OfficeHours. Using the editor framework, I can create OfficeHours
proxies, add them to User and persist() and get the whole graph,
including new OfficeHours, on the server.
If I add a new OfficeHours proxy and update
Any updates on this issue?
It seems very much like a bug as opposed to a purposeful design
choice. All the editors work with object graphs and it makes sense to
persist changes by sending object graph.
On Fri, Oct 15, 2010 at 11:05 AM, Patrick Julien wrote:
> Not to mention that it's right there
Not to mention that it's right there, it's in dvsDataMap, the only
problem is that it's sending the copy from the wrong map, that's it.
On Fri, Oct 15, 2010 at 11:01 AM, Patrick Julien wrote:
> Do you have any idea on how I could get to the modified sub-entity? I
> have no way of reaching it ri
Do you have any idea on how I could get to the modified sub-entity? I
have no way of reaching it right now.
Even if this is outside your design for request factory it kind of
conflicts with the design of editors. Editors want to get an object
graph and that's what we would want to send back since
On Thu, Oct 14, 2010 at 8:17 PM, Patrick Julien wrote:
> As a follow up this, the internal persist() method isn't called on
> these modified entities either.
Chained persistence is explicitly outside the RequestFactory design
because RequestFactory doesn't know anything about persistence.
Introdu
As a follow up this, the internal persist() method isn't called on
these modified entities either.
On Thu, Oct 14, 2010 at 2:40 PM, Patrick Julien wrote:
> and forgot to mention, adding is fine. So if I add a new office hour
> to an existing user, I get a new entity as a child of the user.
>
>
and forgot to mention, adding is fine. So if I add a new office hour
to an existing user, I get a new entity as a child of the user.
Also somewhat related and that I forgot to mention, the user itself,
if modified, is also the right value, and is coming in from dvsDataMap
On Thu, Oct 14, 2010 a
