Multi-page XForms in Separate Deployment

> Has anyone designed a site that contained multi-page XForms in a Orbeon
> separate deployment integration?  If so, how did you resolve the issue of
> needing to keep around the submission XML for multiple pages as the user
> made their changes?
>
> I've been attempting various integration points over the past couple days
> and keep running into issues; not with Orbeon but with the underlying
> technologies involved.  I've tried creating a PageFlow based application and
> housing it within the Orbeon install, but I then run into problems as my
> main application has to figure out how to feed up the XML both for the
> default-submission and for an XSLT transformation.  I tried using the
> URLResouceManager, but ran into problems with the fact that a new session
> gets created when Orbeon makes the URL request over to the main web
> application.  I'm now trying to figure out how I can save the XML out on the
> filesystem somewhere so that my Orbeon PageFlow can pick it up and generate
> the XHTML form.  We will have multiple users in this system, each generating
> XML files that is particular to their needs, so I now run into the question
> of how do I dynamically change the default-submission URL and the URL's
> referenced in my pipeline to support this dynamic nature?  Here's a snippet
> of my pipeline:
>
> <p:processor name="oxf:xslt" xmlns:p="http://www.orbeon.com/oxf/pipeline">
> <p:input name="request" href="#reqParams" />
> <!-- Can this href be set dynamically? -->
> <p:input name="data" href="/myapp/page.jsf" />
> <p:input name="config">
> <xsl:stylesheet version="2.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:import href="dataentry.xsl" /> <!-- stylesheet in same dir as xpl -->
> <xsl:param name="baseUrl"
> select="concat(doc('input:request')/request/scheme, '://',
> doc('input:request')/request/server-name, ':',
> doc('input:request')/request/server-port, '/')" />
> </xsl:stylesheet>
> </p:input>
> <p:output name="data" ref="data" />
> </p:processor>
>
> The above example might be convoluted, but the end goal is to have our main
> web application utilize XForms for a small portion of data entry.  This data
> entry involves multiple pages, which seem to be supported well if utilizing
> Orbeon as your base architecture, but not so much if you use a separate
> deployment.
>
> If anyone has any ideas, comments on what you've tried, etc... I'd love to
> hear them.
>
> --
> ------------------------------------------------------------------------
> Jeremy Nix
> Senior Application Developer
> Cincinnati Children's Hospital Medical Center
>
>
> --
> 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
>
>

> Has anyone designed a site that contained multi-page XForms in a
> Orbeon separate deployment integration?  If so, how did you resolve
> the issue of needing to keep around the submission XML for multiple
> pages as the user made their changes?
>
> I've been attempting various integration points over the past couple
> days and keep running into issues; not with Orbeon but with the
> underlying technologies involved.  I've tried creating a PageFlow
> based application and housing it within the Orbeon install, but I
> then run into problems as my main application has to figure out how
> to feed up the XML both for the default-submission and for an XSLT
> transformation.  I tried using the URLResouceManager, but ran into
> problems with the fact that a new session gets created when Orbeon
> makes the URL request over to the main web application.  I'm now
> trying to figure out how I can save the XML out on the filesystem
> somewhere so that my Orbeon PageFlow can pick it up and generate the
> XHTML form.  We will have multiple users in this system, each
> generating XML files that is particular to their needs, so I now run
> into the question of how do I dynamically change the
> default-submission URL and the URL's referenced in my pipeline to
> support this dynamic nature?  Here's a snippet of my pipeline:
>
> <p:processor name="oxf:xslt" xmlns:p="http://www.orbeon.com/oxf/pipeline">
> <p:input name="request" href="#reqParams" />
> <!-- Can this href be set dynamically? -->
> <p:input name="data" href="/myapp/page.jsf" />
> <p:input name="config">
> <xsl:stylesheet version="2.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:import href="dataentry.xsl" /> <!-- stylesheet in same dir as xpl -->
> <xsl:param name="baseUrl"
> select="concat(doc('input:request')/request/scheme, '://',
> doc('input:request')/request/server-name, ':',
> doc('input:request')/request/server-port, '/')" />
> </xsl:stylesheet>
> </p:input>
> <p:output name="data" ref="data" />
> </p:processor>
>
> The above example might be convoluted, but the end goal is to have
> our main web application utilize XForms for a small portion of data
> entry.  This data entry involves multiple pages, which seem to be
> supported well if utilizing Orbeon as your base architecture, but
> not so much if you use a separate deployment.
>
> If anyone has any ideas, comments on what you've tried, etc... I'd
> love to hear them.
>
> --
> ------------------------------------------------------------------------
> Jeremy Nix
> Senior Application Developer
> Cincinnati Children's Hospital Medical Center

> Jeremy,
>
> Using separate deployment shouldn't change much here: you can POST the
> XML from one page to the next with an<xforms:submission
> replace="all">. See the following:
> http://wiki.orbeon.com/forms/how-to/navigate-to-search-page. And if
> you really want to store XML in the session (which I would really not
> recommend, and use only as a last resort measure!), see:
> http://wiki.orbeon.com/forms/how-to/store-xml-in-the-session. Does
> this help, or did I misunderstand your question?
>
> Alex
>
> On Fri, Jun 25, 2010 at 10:54 AM, Jeremy Nix<[hidden email]>  wrote:
>    
>> Has anyone designed a site that contained multi-page XForms in a Orbeon
>> separate deployment integration?  If so, how did you resolve the issue of
>> needing to keep around the submission XML for multiple pages as the user
>> made their changes?
>>
>> I've been attempting various integration points over the past couple days
>> and keep running into issues; not with Orbeon but with the underlying
>> technologies involved.  I've tried creating a PageFlow based application and
>> housing it within the Orbeon install, but I then run into problems as my
>> main application has to figure out how to feed up the XML both for the
>> default-submission and for an XSLT transformation.  I tried using the
>> URLResouceManager, but ran into problems with the fact that a new session
>> gets created when Orbeon makes the URL request over to the main web
>> application.  I'm now trying to figure out how I can save the XML out on the
>> filesystem somewhere so that my Orbeon PageFlow can pick it up and generate
>> the XHTML form.  We will have multiple users in this system, each generating
>> XML files that is particular to their needs, so I now run into the question
>> of how do I dynamically change the default-submission URL and the URL's
>> referenced in my pipeline to support this dynamic nature?  Here's a snippet
>> of my pipeline:
>>
>> <p:processor name="oxf:xslt" xmlns:p="http://www.orbeon.com/oxf/pipeline">
>> <p:input name="request" href="#reqParams" />
>> <!-- Can this href be set dynamically? -->
>> <p:input name="data" href="/myapp/page.jsf" />
>> <p:input name="config">
>> <xsl:stylesheet version="2.0"
>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>> <xsl:import href="dataentry.xsl" />  <!-- stylesheet in same dir as xpl -->
>> <xsl:param name="baseUrl"
>> select="concat(doc('input:request')/request/scheme, '://',
>> doc('input:request')/request/server-name, ':',
>> doc('input:request')/request/server-port, '/')" />
>> </xsl:stylesheet>
>> </p:input>
>> <p:output name="data" ref="data" />
>> </p:processor>
>>
>> The above example might be convoluted, but the end goal is to have our main
>> web application utilize XForms for a small portion of data entry.  This data
>> entry involves multiple pages, which seem to be supported well if utilizing
>> Orbeon as your base architecture, but not so much if you use a separate
>> deployment.
>>
>> If anyone has any ideas, comments on what you've tried, etc... I'd love to
>> hear them.
>>
>> --
>> ------------------------------------------------------------------------
>> Jeremy Nix
>> Senior Application Developer
>> Cincinnati Children's Hospital Medical Center
>>
>>
>> --
>> 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
>>
>>
>>      
>
>
>