True the form is not ajax, do you think it would help if it was? But even if the PushTarget is triggered with the old data I dont get why the exception is thrown. I would understand if it loads wrong object...but not to get coercion exception, right?
What would be the best way to resolve this issue then? Thanks On Sun, Sep 14, 2014 at 9:24 PM, Lance Java <lance.j...@googlemail.com> wrote: > When a PushTarget renders, it fires up a cometd connection to receive > updates. At this point it registers the page activation context. > > serverside push events fire a component event. But before this, tapestry > first fires the onActivate with the push target's page activation context. > > From your earlier comments, the form submission is not ajax. So I can only > assume a new page render occurs after onSuccess (with a new PushTarget). > > There's likely a situation where the serverside is attempting to push to > the old PushTarget (with the old page activation context value) before the > page refreshes. > -- Sincerely *Boris Horvat*
