Is it possible to do something like this in the page-flow.xml?
<page path-info="/PhyCon/" view="http://localhost:9081/AppName/FormRetrieve?pliID=xxforms:get-request-parameter('pliID')"> So that when I call http://localhost:9080/orbeon/PhyCon/?pliID=15426 the pliID value will get passed along to http://localhost:9081/AppName/FormRetrieve |
Hi,
I don't think you can and that the functionality you need is already built into pageflow. Try something like this (untested) <page id="phy-con" path-info="/PhyCon/" view="PhyCon/view.xhtml" model="PhyCon/model.xpl" default-submission="PhyCon/phy-con.xml"> <setvalue ref="/data/pliID" parameter="pliID"/> </page> phy-con.xml should look like your setvalue ref: <data> <pliID/> </data> When you call http://localhost:9080/orbeon/PhyCon/?pliID=15426 The piece of xml <data> <pliID>15426</pliID> </data> Then gets passed into the model on its instance input. See here: http://www.orbeon.com/orbeon/doc/reference-page-flow#url-extraction Hope that helps, Tom |
Thanks for your help but I want the view link to see the parameter. The reason for this is that the view link is a Servlet and uses the parameter to dynamically retrieve the view from our content repository. This way we don't have to use the file system. It's uses the url parameter passed in to uniquely identify the form. This method worked for me.
<page path-info="/PhyCon/([^/]+)" view="http://localhost:9081/DMWeb/FormRetrieve?pliID=${1}" matcher="oxf:perl5-matcher"> <setvalue ref="pliID" parameter="pliID"/> </page> so a URL of "http://localhost:9081/orbeon/PhyCon/12345" would call the FormRetrieve servlet. The servlet would then be aple to see that url parameter pliID=12345 Paul |
Administrator
|
Paul,
So you would like to create a sort of "proxy", so users don't see the URL http://localhost:9081/DMWeb/FormRetrieve?pliID=${1} but instead see http://localhost:9081/orbeon/PhyCon/12345. Is that it? The page flow controller has not been designed to act as a proxy. What does http://localhost:9081/DMWeb/FormRetrieve return? Does it return the XForms code that then needs to be processed? If that is the case, then I would map /PhyCon to an XPL that retrieves the XForms using the URL generator, with a config generated dynamically in XSLT based on information provided by the request generator. Alex On Mon, Mar 29, 2010 at 7:38 AM, paul8226 <[hidden email]> wrote: > > Thanks for your help but I want the view link to see the parameter. The > reason for this is that the view link is a Servlet and uses the parameter to > dynamically retrieve the view from our content repository. This way we > don't have to use the file system. It's uses the url parameter passed in to > uniquely identify the form. This method worked for me. > > <page path-info="/PhyCon/([^/]+)" > view="http://localhost:9081/DMWeb/FormRetrieve?pliID=${1}" > matcher="oxf:perl5-matcher"> > <setvalue ref="pliID" parameter="pliID"/> > </page> > > so a URL of "http://localhost:9081/orbeon/PhyCon/12345" would call the > FormRetrieve servlet. The servlet would then be aple to see that url > parameter pliID=12345 > > Paul > -- > View this message in context: http://n4.nabble.com/Accessing-request-parameter-in-the-page-flow-xml-tp1692440p1695179.html > Sent from the Orbeon Forms (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, open-source, for the Enterprise - http://www.orbeon.com/ My Twitter: http://twitter.com/avernet -- 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
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Free forum by Nabble | Edit this page |