Don,
Not sure that I understand what you want, but making that assumptions,
let's suppose the called XPL contains an input declaration like this:
<p:param name="instance" type="input"/>
...then your XSLT processor somewhere in that XPL can access the
instance like this:
<p:processor name="oxf:xslt">
<p:input name="data" href="#instance"/>
<p:input name="config">
...your XSLT stylesheet here...
</p:input>
<p:output name="data" ref="something"/>
</p:processor>
HTH
A.
On Nov 8, 2005, at 5:38 PM, Smith, Donald wrote:
> I don’t understand how to access pipeline output in similar fashion to
> accessing action output.
>
> That is, I know how to use the “action” attribute on a <action>
> element in the page-flow.xml, and how to access the result of running
> an XSLT transform on the form instance using ‘oxf:action’ (down inside
> the <result> element).
>
> But I can’t figure out how to accomplish the same thing if I run my
> transform through a pipeline.
>
> So let’s say I have a pipeline that gets called given a certain action
> on a page. Part of the pipeline is to call an XSLT transform on the
> form instance. I know this works because I can serialize the result
> out to file. Now, instead of serializing the result, I want to access
> the result exactly the same way that I would if I had just called the
> XSLT using the attribute “action”. How do I do that?
>
> Thanks,
>
> Don
>
> --
> 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
Locked
