Hi Gary,
We hit the same issue last week. It is a bug in the new rhino jar. Same
as you all our flow applications fails with the new rhino introduced in
2.1.10.
We also spent 2 days trying to fix it inside the rhino code. Our work
around after 2 days was to continue using
rhino1.5r4-continuations-R26.jar. The latest cocoon revision using the
later jar on subversion is 479984.
Best Regards,
Antonio Gallardo.
Gary Larsen escribió:
I just tried my application using 2.1.9 and the forms/continuations are
working OK. This Cocoon version is using rhino1.5r4-continuations-R26.jar
so I would like to move to 2.1.10 if possible.
I'm not sure if this is a problem of my configuration/code compatibilty with
2.1.10 or possibly a bug in that version.
Any suggestions on how a non-cocoon-dev person can track down this problem
(if that's possible :-) would be great.
Thanks,
Gary
hi Gary, would you confirm if the issue is similar to:
http://issues.apache.org/jira/browse/COCOON-1579
The issue is similar in that I'm using a flow function and jx
template with a continuation. The behavior is reversed as my
first continuation throws an exception and after that the
continuations work.
My exception is thrown at FOM_Cocoon.jsGet_request (rather than
FOM_Cocoon.jsGet_continuation) but my guess is that they are
both due to currentCall being null.
