Hi,
We've noticed that, when using the workflow-send button with a page of our own to which orbeon posts the xml, it is possible for the client to leave the page during the save process, after which orbeon does not even call the final landing page. (we are using orbeon 3.9, and I made a small change in persistence-model.xml to have the document id, app and form in the url parameters, inspired by the newer version in your source on github, but using concat instead of the formrunner's query building method) This did not happen in manual testing, because we weren't fast enough and waited for the result after clicking the workflow-send button, but it did happen when using a script to do a load-test, which just watches for the "document saved" message which appears when still on the edit/new page. It happened completely silently, without any error in the logs. It may not be a big problem, but it becomes one when the backend system depends on orbeon posting a message to our landing page; it has to happen whenever the workflow-send is used. Is this a bug, or perhaps a misconfiguration on our side? What work-around would you suggest? Sincerely, Koen Vanderkimpen Research/Recherche/Onderzoek Connect: -- 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 |
Free forum by Nabble | Edit this page |