Hi,
I have an integrated java application that is generating XForm pages via servlets and passing them off to Orbeon for processing to the browser via the predefined request attribute: "oxf.xforms.renderer.document". // as per http://www.orbeon.com/ops/doc/reference-xforms-java req.setAttribute("oxf.xforms.renderer.document", xformsDoc); This mechanism is working fine in Orbeon 3.6.0, and I have also tried it successfully with a later 3.7 build (3.7.0beta1+.200904040015), however I have since tried the latest 3.7.1 developer release and it no longer appears that OPS is picking up my form that I set via this attribute. Instead it seems as though the the servlet filter isnt being called, or is returning early before any handling of the form. I have turned logging up and still see no information that the servlet filter is being run. If I replace the core orbeon jars in my application from the 3.7.1 developer release back to 3.7.0beta1+.200904040015, things start to work again, so I believe my configuration is correct. Has anyone came across a similar problem ? I am running WAS v6.1. but I do not think this is a platform specific issue. AFAIK, this might be caused by some recent changes in OrbeonXformsFilter, but I havent checked out the latest source to verify. Regards, Murray |
I would like to mention that I am upgrading from v3.6.0 to v3.7.1. So there might be some configuration settings that have changed between these two versions that are causing this inconsistency. |
Administrator
|
In reply to this post by Murray M
Murray,
I am not sure why this is not working for you. The oxf.xforms.renderer.document" parameter is still used. Do you have the ability of debugging the Java code? If so, a breakpoint in the filter might tell you if it is called at all, and if so if something wrong is going on in the filter itself. -Erik On Jun 12, 2009, at 1:01 PM, Murray M wrote: > > Hi, > > I have an integrated java application that is generating XForm pages > via > servlets and passing them off to Orbeon for processing to the > browser via > the predefined request attribute: "oxf.xforms.renderer.document". > > // as per http://www.orbeon.com/ops/doc/reference-xforms-java > req.setAttribute("oxf.xforms.renderer.document", xformsDoc); > > This mechanism is working fine in Orbeon 3.6.0, and I have also > tried it > successfully with a later 3.7 build (3.7.0beta1+.200904040015), > however I > have since tried the latest 3.7.1 developer release and it no longer > appears > that OPS is picking up my form that I set via this attribute. > Instead it > seems as though the the servlet filter isnt being called, or is > returning > early before any handling of the form. > > I have turned logging up and still see no information that the servlet > filter is being run. > > If I replace the core orbeon jars in my application from the 3.7.1 > developer > release back to 3.7.0beta1+.200904040015, things start to work > again, so I > believe my configuration is correct. > > Has anyone came across a similar problem ? I am running WAS v6.1. > but I do > not think this is a platform specific issue. > > AFAIK, this might be caused by some recent changes in > OrbeonXformsFilter, > but I havent checked out the latest source to verify. > > Regards, > Murray > > > -- > View this message in context: http://www.nabble.com/Issues-passing-XForms-document-as-%22oxf.xforms.renderer.document%22-in-3.7.1-tp24005276p24005276.html > Sent from the ObjectWeb OPS - Users mailing list archive at > Nabble.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 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 |
Hi Erik,
I grabbed the source for 3.7.1 and started to look at OrbeonXformsFilter. It seems to me that there was a change in the call to the xforms-renderer which used to be unconditional, but now has a check to see if there is any content in the servlet response: // Forward to Orbeon Forms for rendering only of there is content to be rendered, otherwise just return and // let the filterChain finish its life naturally, assuming that when sendRedirect is used, no content is // available in the response object if (!isBlank(responseWrapper.getContent())) getOPSDispatcher(OPS_RENDERER_PATH).forward(httpRequest, httpResponse); So I think this was the 'early exit' I was seeing in my application, since I am setting the attribute in the session for passing the xforms document, and there is not necessarily any content in the response. In a previous post of yours, you happened to include the latest source for the xforms-filter where this check has since changed to the following: // Forward to Orbeon Forms for rendering if (responseWrapper.isForwardable()) getOPSDispatcher(OPS_RENDERER_PATH).forward(httpRequest, httpResponse); So I haven't checked the latest source to see if this fixes the problem ( I am assuming it does ), but I will post back here later once I test it out. Many thanks, Murray
|
Free forum by Nabble | Edit this page |