Re: First time continuation exception (2.1.10 upgrade)

2007-01-24 Thread Mark Lundquist
On Jan 24, 2007, at 5:45 AM, Gary Larsen wrote: Yep, this is a similar problem where currentCall is null. Bypassing the NPE doesn't work with sendForm() since it will then NPE on the form.save(). Right :-/ There must be something wrong with my configuration or component version somewhere.

RE: First time continuation exception (2.1.10 upgrade)

2007-01-24 Thread Gary Larsen
Thanks Mark, > Certainly the NPE results from the FOM_Cocoon object having a null > value for its currentCall instance variable. A few months ago I had to > add some AJAX features to a previously non-AJAX-using application built > on Cocoon 2.1.8, and I was getting a similar failure, but mine was

Re: First time continuation exception (2.1.10 upgrade)

2007-01-23 Thread Mark Lundquist
On Jan 23, 2007, at 1:33 PM, Gary Larsen wrote: Sorry for another 2.1.10 upgrade question. I've been able to tackle most of the cforms issues but this has me stuck. The first time a session calls any continuation an exception occurs with an NPE in org.apache.cocoon.components.flow.javasc

First time continuation exception (2.1.10 upgrade)

2007-01-23 Thread Gary Larsen
Sorry for another 2.1.10 upgrade question. I've been able to tackle most of the cforms issues but this has me stuck. The first time a session calls any continuation an exception occurs with an NPE in org.apache.cocoon.components.flow.javascript.fom.FOM_Cocoon.jsGet_request. After that continuati