Question

We are integrating Form Runner/Builder into a project with a custom persistence layer.

Right now we have emptySessionPath=”true” set to keep Orbeon and our Java app on the same session.

Orbeon is passing the jsessionid cookie in the persistence CRUD calls… except for the following instance….

1. User connects to our Java app and logs in, jsessionid cookie is set
2. User visits an existing form instance at /fr/OurApp/formtest/edit/3eb4ddcf03f2410084e5578adb1e2a7b (Session Cookie is present)
3. Persistence call is made to our custom persistence layer, but cookie is not forwarded

But, if the user was to first edit the form itself with a call to /fr/orbeon/builder/edit/f40efbe298204d16b6474fcdfea4c9fd which does pass the cookie to the persistence layer

At this point the user can go visit step 2 to complete the form instance and the cookie will persist. It seems that for some reason starting form builder is required to get the cookie to forward to the persistence layer when completing the form?

Any ideas on why the cookie isn’t getting passed on step 2?

FYI this is on Orbeon 3.9 CE, also same behavior in 3.8. Using VMWare TC Server (Tomcat). Our java app is a Spring/Grails app.

Answer 1

I am wondering if this might be what’s described in this bug (see in particular the comments). Basically, it doesn’t seem like you can always reliably produce a JSESSIONID cookie. And as the bug says, we don’t have a solution right now.

Do you think the bug corresponds to your case?