Error While Producing Form for JavaScript Embedding API

Aaron Spike

unread,

Sep 20, 2021, 11:34:08 AM9/20/21

to Orbeon Forms

I didn't see any errors like this while testing, but of course, once we've moved to production weird things are happening. When a user saves a form with the new server that had previously been saved with the old server we see the following situation. For embedded forms, view mode works, but edit mode fails with the "link" error below.

How should I go about troubleshooting this problem?

+----------------------------------------------------------------------------------------------------------------------+

|An Error has Occurred |

|----------------------------------------------------------------------------------------------------------------------|

|Fatal error: The element type "link" must be terminated by the matching end-tag "</link>". |

|----------------------------------------------------------------------------------------------------------------------|

|Application Call Stack |

|----------------------------------------------------------------------------------------------------------------------|

|oxf:/apps/fr/detail/read-form.xpl |reading processor output | 91|

|······················································································································|

|element=<p:output name="data" id="document"/> |

|name =data |

|id =document |

|----------------------------------------------------------------------------------------------------------------------|

|ions/Application/form/form.xhtml?document=236ce9f8666bb70de66d4e9396d2d669aaa6d3b5| | 1|

|oxf:/page-flow.xml |reading page model data output| 31|

|······················································································································|

|element=<page path="/([^/]+)/.*" model="apps/${1}/page-flow.xml" public-methods="#all"/> |

|model =apps/${1}/page-flow.xml |

|----------------------------------------------------------------------------------------------------------------------|

|oxf:/apps/fr/detail/read-form.xpl |executing processor | 96|

|······················································································································|

|element=<p:processor name="oxf:null-serializer">[...]</p:processor> |

|name ={http://www.orbeon.com/oxf/processors}null-serializer |

|----------------------------------------------------------------------------------------------------------------------|

|Exception: org.orbeon.oxf.common.ValidationException |

|----------------------------------------------------------------------------------------------------------------------|

Aaron Spike

unread,

Sep 20, 2021, 2:15:10 PM9/20/21

to Orbeon Forms

In hopes of troubleshooting the problem:

I tried copying read-form.xpl from github
placing it in the appropriate place in my application
putting a debug attribute on the inputs and outputs
inspecting the data for invalid xml

But between #2 and #3, the form started loading. After removing read-form.xpl and restarting the server, it still works. I can't explain this, and I have a feeling the error will come back.

The next problem, sometimes I get 403 Unauthorized when attempting to edit a form in Orbeon Forms server while at the same time the form works perfectly well embedded in view and edit mode. View mode on Orbeon Forms server still works. I can't help but wonder if this has something to do with leases, but I thought they were turned off by default.

Is there some way to see the effective properties for a currently running Orbeon Forms server instance?

Aaron Spike

unread,

Sep 20, 2021, 3:03:51 PM9/20/21

to Orbeon Forms

And, yes, after a while the 500 error for the embedded form about the unclosed <link/> element comes back.

I should also note that the 403 in Form Runner goes away for a while just after tomcat is restarted.

Alessandro Vernet

unread,

Sep 20, 2021, 4:20:58 PM9/20/21

to Orbeon Forms

Hi Aaron,

The element type "link" must be terminated by the matching end-tag "</link>

I would suspect that this is caused by "someone" returning HTML (which maybe contains an error), while Orbeon Forms expects XML. If you can reproduce this, if you'd like to attach an `orbeon.log` in dev mode, I'll check it to see if I can find what it is.

The next problem, sometimes I get 403 Unauthorized when attempting to edit a form in Orbeon Forms server while at the same time the form works perfectly well embedded in view and edit mode.

Are users logged in? Do you have permissions on your form? Do you have anything that could explain the `JSESSIONID` not always making it to Orbeon Forms (e.g. reverse proxy, clustering)?

Is there some way to see the effective properties for a currently running Orbeon Forms server instance?

There is no UI showing the values of the current properties.

-Alex

This electronic communication, including any attached documents, may contain confidential and/or legally privileged information that is intended only for use by the recipient(s) named above. If you have received this communication in error, please notify the sender immediately and delete the communication and any attachments. Views expressed by the author do not necessarily represent those of Martin Luther College.
--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orbeon+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/f33d9a39-2d91-46e7-bd02-4b35348da2b4n%40googlegroups.com.

ebruchez

unread,

Sep 20, 2021, 5:03:17 PM9/20/21

to Orbeon Forms

> There is no UI showing the values of the current properties.

There no UI but setting this in log4j.xml will log all properties when Orbeon Forms starts:

</category>

-Erik

Aaron Spike

unread,

Sep 20, 2021, 6:12:11 PM9/20/21

to Orbeon Forms

On Monday, September 20, 2021 at 4:03:17 PM UTC-5 ebruchez wrote:

> There is no UI showing the values of the current properties.

There no UI but setting this in log4j.xml will log all properties when Orbeon Forms starts:

<category name="org.orbeon.properties">
<priority value="debug"/>
</category>

This is what I remember, but I couldn't find the output in the orbeon.log file. I'll check again. Thanks.

Aaron Spike

unread,

Sep 23, 2021, 2:22:53 PM9/23/21

to Orbeon Forms

This worked for me. But interestingly when I search the documentation site for "org.orbeon.properties" no results are returned. Where should I have looked to rediscover this information?

On Monday, September 20, 2021 at 4:03:17 PM UTC-5 ebruchez wrote:

Aaron Spike

unread,

Sep 23, 2021, 2:29:17 PM9/23/21

to Orbeon Forms

I was able to reproduce both of my issues and capture log files. It seems that whatever method I used to open the form first succeeds and the second fails with each failure manifesting in a different error. Is there a customer support portal where I can send these log files?

Alessandro Vernet

unread,

Sep 23, 2021, 5:39:54 PM9/23/21

to Orbeon Forms

Hi Aaron,

You can just attach your logs to a response here. (We have a support portal for PE customers.) Also, could you record a video of what the problem you're describing looks like (you could also attach it, or post it somewhere)? This would help provide us some context, as I don't quite picture what you described as "whatever method I used to open the form first succeeds and the second fails".

-Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/4b010c8a-e6e7-48b1-acc7-c8350e2a53ddn%40googlegroups.com.

Reply all

Reply to author

Forward