Similar problem, but I was not able to implement your solution - any
guidance is suggested. And I promise, once I get my simple app
working, I will write the GWT/Objectify 1-to-Many Relationships for
Moron Like Me guide :).
The problem in the small...
CommitUsers can have Commitments. I create
Problem solved...
I was confused about two key points (sadly confusion is an
occupational hazard for us morons):
1) When to reuse a RequestContext vs. creating a new RequestContext
2) What Objectify.put() actually does
For #1, I believe that the same dynatablerf code put it as using the
given
Thanks Tobias,
That explanation was good. I had it right logically, but omitted
calling one of my special - create me a new methods, that replaced
my RequestContext for me.
All good niow. it saves data!
On Nov 9, 2:28 pm, Tobias thaberm...@gmail.com wrote:
I *think* that happens after you
Hi All,
I am currently in the process of building an app, initally based off
the Roo framework.
I am getting a A request is already in progress at the point where I
call create for a child entity.
Is there a way I can see what request contexts are in progress, so I
can debug where my logic is
I *think* that happens after you have fired a RequestContext. From
looking at the code, which is a bit hard because of the
DeferredBinding that's going on there, the locked variable in a
RequestContext gets only reset to false, if the fired Request fails.
So I think you need to use a new
