xforms:upload controls interfere with submissions triggered by xforms-ready

We've been working on a task which involves sending a submission on xforms-ready, and we've discovered that this stops working if the instance to be submitted has an upload control bound to a node in the instance to be submitted.  See the attached example, upload-and-xforms-ready.html (obviously the action URL needs to be replaced with some suitable echo servlet or xpl available locally).

In the example, there are two instances, and a submission has the effect of copying the first instance to the second.  This submission can be sent by pressing the trigger, but it should also be sent on xforms-ready.  However, with the upload control bound to a node in instance one the submission does not get sent.  From what I can tell through log4j debugging, the xforms-submit event does get dispatched to the submission, but the xforms-submit-serialize event does not get dispatched.

As a workaround, it is possible to set the instance to be submitted to be not relevant (marking the submission with relevant="false") and then set the instance to be relevant when the first submission completes.  See the attached file upload-and-xforms-ready-workaround.xhtml.

Cheers,

Dave McIntyre

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

David,

 > We've been working on a task which involves sending a submission on
 > xforms-ready, and we've discovered that this stops working if the
 > instance to be submitted has an upload control bound to a node in
 > the instance to be submitted.  See the attached example,
 > upload-and-xforms-ready.html (obviously the action URL needs to be
 > replaced with some suitable echo servlet or xpl available locally).
 >
 > In the example, there are two instances, and a submission has the
 > effect of copying the first instance to the second.  This submission
 > can be sent by pressing the trigger, but it should also be sent on
 > xforms-ready.  However, with the upload control bound to a node in
 > instance one the submission does not get sent.  From what I can tell
 > through log4j debugging, the xforms-submit event does get dispatched
 > to the submission, but the xforms-submit-serialize event does not
 > get dispatched.
 >
 > As a workaround, it is possible to set the instance to be submitted
 > to be not relevant (marking the submission with relevant="false")
 > and then set the instance to be relevant when the first submission
 > completes.  See the attached file
 > upload-and-xforms-ready-workaround.xhtml.

Thanks for the bug report. I think I fixed this. Here is the bug entry
for reference:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=307803&group_id=168&atid=350207

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws