Posted by
Ralf Jung on
Mar 17, 2011; 8:22pm
URL: https://discuss.orbeon.com/Exception-in-xforms-js-tp3345793p3385574.html
Hi Erik,
> We have some doc on the differences between 3.8 and 3.9 uploads here:
>
>
http://wiki.orbeon.com/forms/doc/developer-guide/xforms-controls/upload-con> trol#TOC-With-Orbeon-Forms-3.9
>
> 3.9 no longer dispatches xforms-select, as the upload now starts
> automatically. We could have kept xforms-select, but then with existing
> code that would trigger the "fake" submission hack used in 3.8, and that
> in turn could cause issues. So we decided instead to not dispatch
> xforms-select anymore, and to use new events to clearly indicate the start
> and end of an upload.
>
> It is unfortunate that a code change is needed, but the upload
> implementation was changed in quite a major way and we are not sure a
> backward-compatible solution is possible (ideas welcome).
I perfectly understand that, and if I had to decide, that's what I had done -
dragging old broken APIs around is always bad. In this case however it means I
can't test this part of my app with the new Orbeon before there is a stable
release with the changed API.
> Now back to the original issue: what you say seems to indicate that there
> is an unescaped in the response, and there probably shouldn't be
> one.
>
> Can you see with Firebug what's the content of the Ajax or pseudl-Ajax
> response reaching the client? If not with Firebug, with HTTPScoop or
> similar:
>
>
http://wiki.orbeon.com/forms/doc/developer-guide/admin/monitoring-http-requ> ests
>
> Or, is there any way we can reproduce this locally?
I would not know how - as I said, I have two upload fields, and for one of
them, triggering the submission when the upload is finished works perfectly
fine.
To make things even more weird: The error is only triggered by some files I
upload. Those files contain a search query that is then executed on the
database, and the character it complains about is part of the list of search
results that gets sent from the server to the form. The error somehow depends
on the set of resulting items. However, in any way, the *same* result set is
transmitted perfectly fine if I do the search the normal way, i.e. without
using an uploaded file.
I will grab a server reply that's causing the error via Wireshark and send it
to you via personal mail.
Kind regards,
Ralf
--
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