OK, for me, this has nothing to do with find, at least not yet, I
don't even get that far. What's tripping me up is that up until now,
we could always get back the id of the entity in
AbstractProxyEditActivity before the find request had completed but
now, getRecord() returns null, this is expected considering find
hasn't completed.
So in start(AcceptsOneWidget display, EventBus eventBus) {
// delay
// getId to get some child owned resources, now getRecord() returns
null so getRecord().getId() throws NPE
}
and then later really start the display by calling super.start where
super is AbstractProxyEditActivity
we can work around this but I'm still taking the time to expose the
issue here.
That and I'm still not sure how we implement find on our end in the
server with this new mechanism
On Mon, Sep 20, 2010 at 3:05 PM, Patrick Julien <[email protected]> wrote:
> On Mon, Sep 20, 2010 at 3:03 PM, Ray Ryan <[email protected]> wrote:
>> Ah, I noticed that exception in the find method too. I thought I had
>> introduced the problem, but I think instead I just started using the feature
>> for the first time.
>> Patrick, is the exception reliable? Do you have a recipe?
>
>
> I'm just started on this but yes, it is definitely reliable, it always fires
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
