Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of gary.larsen@envisn.com
 designates 216.57.116.8 as permitted sender)
From: "Gary Larsen" <gary.larsen@envisn.com>
To: <users@cocoon.apache.org>
Subject: RE: First time continuation exception (2.1.10 upgrade)
Date: Wed, 24 Jan 2007 08:45:28 -0500
Message-ID: <006201c73fbd$e93d0e50$4f01a8c0@envisnofc.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <6bf0f2a584b0351975c322219805f78c@gmail.com>
thread-index: Acc/P7GwWqhJG2xNRcO6hcjkCwK8hAAfRyIg

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 in
> jsGet_continuation().  I can't remember why currentCall was null in my
> case, unfortunately I didn't document this incident and now I don't
> recall the details... but I'm pretty sure I remember being certain that
> this was normal and not caused by anything I was doing wrong.  I made a
> local fix in FOM_Cocoon to have jsGet_continuation() return null if
> currentCall was null.

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().

There must be something wrong with my configuration or component version
somewhere.  My geekhat's a bit loose but hopefully I can track it down :-)

Gary


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org