Hi,
I'm trying to debug a pipeline with an XSL transform defined inside a for-each, such as: <p:processor name="oxf:xslt"> <p:input name="data" href="#instance" debug="instance"/> <p:input name="foo" href="#foo" debug="foo"/> <p:input name="current" href="current()" debug="current"/> <p:input name="bar" href="#bar" debug="bar"/> <p:input name="config"> <xsl:stylesheet version="2.0"> <!-- skipped --> </xsl:stylesheet> </p:input> <p:output name="data" id="myOutput"/> </p:processor> But I've noticed only some of the inputs are displayed in the log... For instance, I see "foo" but not "bar". Any idea why this would be happening? cheers, alex -- 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 |
I can't really tell from your example, but it could be because input bar is never read. Orbeon Forms, despite the top-down impression of XPL works backwards. It starts at the outputs, discovers what processor it needs to create that input, and tries to run that processor. That processor determines what processors are needed to crate the relevant output. So on and so forth.
This doesn't apply for @debug attributes. They will log the instance when data passes through them, but they won't trigger the dependency if that input is not needed. If I'm wrong, and you are indeed consuming input "bar"... then I don't know. We'd probably need to see more of your code. -- Daniel E. Renfer http://kronkltd.net/ On 6/20/07, Alex Boisvert <[hidden email]> wrote: Hi, -- 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 |
Daniel,
Thanks for you answer . My use-case is a bit convoluted to post on the mailing list... so I'll follow with a quick question instead. Do you know if using the input value in the XSLT processor such as: <xsl:value-of select="doc('input:bar')"/> Is enough to trigger the dependency on <p:input name="bar" href="#bar" debug="bar"/> ? cheers, alex On 6/20/07, Daniel E. Renfer <[hidden email]> wrote: I can't really tell from your example, but it could be because input bar is never read. Orbeon Forms, despite the top-down impression of XPL works backwards. It starts at the outputs, discovers what processor it needs to create that input, and tries to run that processor. That processor determines what processors are needed to crate the relevant output. So on and so forth. -- 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 |
Alex,
I don't think the input alone will not be enough to trigger
it to be read ..... when I come across this problem I just tend to put an empty
if statement in my xslt .... something like this works ...
<xsl:variable name="bar"
select="doc('input:bar')"/>
<xsl:if test="count($bar) >
0">
</xsl:if>
HTH
Steve
STEVE
LENHART
WEB
DEVELOPER
TELEFLEX CORPORATE IT
155 SOUTH
LIMERICK ROAD
LIMERICK, PA
19468
TEL>
610-948-1744
MOB>
484-919-5578
EMAIL>
[hidden email]
-- 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 |
Thanks, that worked!
On 6/21/07, Steve Lenhart <[hidden email]> wrote:
-- 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 |