[ http://issues.apache.org/jira/browse/COCOON-1812?page=all ]
Ugo Cei closed COCOON-1812:
---------------------------
Fix Version: 2.1.9-dev (current SVN)
Resolution: Fixed
Patch applied.
> Javaflow and Ajax when sending two forms one after eachother
> ------------------------------------------------------------
>
> Key: COCOON-1812
> URL: http://issues.apache.org/jira/browse/COCOON-1812
> Project: Cocoon
> Type: Bug
> Components: Blocks: Forms, Blocks: Java Flow
> Versions: 2.1.9-dev (current SVN)
> Reporter: Simone Gianni
> Priority: Critical
> Fix For: 2.1.9-dev (current SVN)
> Attachments: javaflow-ajax.diff
>
> In javaflow, if I try to send an ajax form and then send another ajax form I
> obtain a NPE originating from JXMacroHelper.
> For example :
> FormInstance fi = new FormInstance("myform.def.xml");
> fi.show("mypipe");
> fi = new FormInstance("myotherform.def.xml");
> fi.show("myotherpipe");
> I receive an NPE originating from JXMacroHelper:162 while showing the second
> forms.
> After investigations i noticed that the second form was displayed following
> the ajax behaviour, while this second form is new and should not be "ajaxed".
> This causes the updatedWidgets list to be null (both in form and in
> JXMacroHelper) and thus the NPE.
> Sniffing the http traffic showed me that while in javascript the submission
> of the first form causes a <bu:continue/> and a new non-ajax request from the
> browser, while with javaflow this does not happen.
> Seems like the lines from 176 to 201 of
> /cocoon-2.1.X/src/blocks/forms/java/org/apache/cocoon/forms/flow/javascript/Form.js
> were not ported to the javaflow FormInstance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
