Case 1 working OK
<page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xhtml"/> I have in the xhtml file <f:instance id="artefact_data"> <xi:include href="input:data"/> </f:instance> where the input:data are coming from the run-detail.xpl on the model. Case 2 <page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xpl"/> The artefactfull.xpl serves for the moment as an identity transform of file artefactfull.xhtml with the result on output:data on the view. The identity transform of artefactfull.xhtml indeed works, but <f:instance id="artefact_data"> <xi:include href="input:data"/> </f:instance> doesn't seem to pick up the run-detail.xpl generated data anymore. What needs to be changed for this scenario? -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Case 1 working OK
<page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xhtml"/> I have in the xhtml file <f:instance id="artefact_data"> <xi:include href="input:data"/> </f:instance> where the input:data are coming from the run-detail.xpl on the model. Case 2 <page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xpl"/> The artefactfull.xpl serves for the moment as an identity transform of file artefactfull.xhtml with the result on output:data on the view. The identity transform of artefactfull.xhtml indeed works, but <f:instance id="artefact_data"> <xi:include href="input:data"/> </f:instance> doesn't seem to pick up the run-detail.xpl generated data anymore. What needs to be changed for this scenario? -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
In reply to this post by paul.hermans
I'm pretty sure that oxf:identity doesn't process XInclude. If you
want to include the instance, you might want to check out oxf:xinclude http://www.orbeon.com/ops/doc/processors-xinclude#d39e33 Daniel E. Renfer http://kronkltd.net/ On 11/17/06, [hidden email] <[hidden email]> wrote: > Case 1 working OK > <page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xhtml"/> > > I have in the xhtml file > <f:instance id="artefact_data"> > <xi:include href="input:data"/> > </f:instance> > > where the input:data are coming from the run-detail.xpl on the model. > > Case 2 > <page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xpl"/> > > The artefactfull.xpl serves for the moment as an identity transform of file artefactfull.xhtml with the result on output:data on the view. > > The identity transform of artefactfull.xhtml indeed works, but > <f:instance id="artefact_data"> > <xi:include href="input:data"/> > </f:instance> > doesn't seem to pick up the run-detail.xpl generated data anymore. > > What needs to be changed for this scenario? > > > > > -- > 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 > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > > -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
In reply to this post by Paul Hermans-2
Paul,
Automatic XInclude processing is performed directly on the view. If your view is a static XML (XHTML, etc.) file, XInclude applies to this. If XSLT, XInclude applies to the XSLT stylesheet before the stylesheet is processed. If XPL, XInclude applies to the XPL pipeline before it is processed. So unless your XForms code is inline within the XPL pipeline, it won't have automatic XInclude processing. What you need to do is manually use the oxf:xinclude processor to perform XInclude processing on your XForms document. -Erik Paul Hermans wrote: > Case 1 working OK > <page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xhtml"/> > > I have in the xhtml file > <f:instance id="artefact_data"> > <xi:include href="input:data"/> > </f:instance> > > where the input:data are coming from the run-detail.xpl on the model. > > Case 2 > <page path-info="/spil-edit/detail" model="services/run-detail.xpl" view="artefactfull.xpl"/> > > The artefactfull.xpl serves for the moment as an identity transform of file artefactfull.xhtml with the result on output:data on the view. > > The identity transform of artefactfull.xhtml indeed works, but > <f:instance id="artefact_data"> > <xi:include href="input:data"/> > </f:instance> > doesn't seem to pick up the run-detail.xpl generated data anymore. > > What needs to be changed for this scenario? Orbeon Forms - XForms Everywhere http://www.orbeon.com/blog/ -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Free forum by Nabble | Edit this page |