unconnected processors skipped?!

I've got a pipeline which has no outputs, only inputs. I've been having trouble getting it to run: nothing seems to happen, even with debug attributes throughout nothing is logged.

I'm using the Java API to execute & read output from the pipeline.

I've found that processors which aren't eventually connected to outputs of the pipeline *which are then read* aren't seeming to get executed. For example, in the attached pipeline the delegation processor should throw an error because the address isn't invalid: instead, the delegation processor seems to get skipped altogether & the pipeline runs ok.

If you modify the final xslt processor to use the web-service-result document as an input (instead of web-service-call), then the delegation process is run, and you get the expected error. This seems totally wrong!

Adrian

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

<?xml version="1.0"?>
<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
		xmlns:oxf="http://www.orbeon.com/oxf/processors"
		xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
		xmlns:xi="http://www.w3.org/2001/XInclude"
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	
	<p:param type="output" name="data" />
	<p:param type="input" name="data"/>
	
	<p:processor name="oxf:xslt">
		<p:input name="data" href="#data"/>
		<p:input name="config">
			<hwynums xsl:version="2.0">
				<xsl:value-of select="/parameters/highway"/>
			</hwynums>
		</p:input>
		<p:output name="data" id="xslt-result"/>
	</p:processor>
	
	<p:processor name="oxf:xinclude">
		<p:input name="config">
			<delegation:execute service="ca-traffic" operation="getTraffic" xmlns:delegation="http://orbeon.org/oxf/xml/delegation">
				<xi:include href="input:xslt-result"/>
			</delegation:execute>
		</p:input>
		<p:input name="xslt-result" href="#xslt-result"/>
		<p:output name="data" id="web-service-call"/>
	</p:processor>
	
	<p:processor name="oxf:delegation">
		<p:input name="interface">
			<config>
				<service id="ca-traffic" type="webservice" endpoint="http://s121212121212dfdfervices.xmethods.net/soap/servlet/rpcrouter">
					<operation nsuri="urn:xmethods-CATraffic" name="getTraffic"/>
				</service>
			</config>
		</p:input>
		<p:input name="call" href="#web-service-call"/>
		<p:output name="data" id="web-service-result" debug="true"/>
	</p:processor>
	
    <p:processor name="oxf:xslt">
        <p:input name="data" href="#web-service-call"/>
        <p:input name="config">
            <xsl:stylesheet version="2.0">
                <xsl:import href="oxf:/oxf/xslt/utils/copy.xsl"/>
                <xsl:template match="/">
                    <xsl:copy-of select="." copy-namespaces="no"/>
                </xsl:template>
            </xsl:stylesheet>
        </p:input>
        <p:output name="data" ref="data"/>
    </p:processor>	

</p:config>

  

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

I've got a pipeline which has no outputs, only inputs. I've been having trouble getting it to run: nothing seems to happen, even with debug attributes throughout nothing is logged.

I'm using the Java API to execute & read output from the pipeline.

I've found that processors which aren't eventually connected to outputs of the pipeline *which are then read* aren't seeming to get executed. For example, in the attached pipeline the delegation processor should throw an error because the address isn't invalid: instead, the delegation processor seems to get skipped altogether & the pipeline runs ok.

If you modify the final xslt processor to use the web-service-result document as an input (instead of web-service-call), then the delegation process is run, and you get the expected error. This seems totally wrong!

Adrian

<?xml version="1.0"?>
<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
		xmlns:oxf="http://www.orbeon.com/oxf/processors"
		xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
		xmlns:xi="http://www.w3.org/2001/XInclude"
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	
	<p:param type="output" name="data" />
	<p:param type="input" name="data"/>
	
	<p:processor name="oxf:xslt">
		<p:input name="data" href="#data"/>
		<p:input name="config">
			<hwynums xsl:version="2.0">
				<xsl:value-of select="/parameters/highway"/>
			</hwynums>
		</p:input>
		<p:output name="data" id="xslt-result"/>
	</p:processor>
	
	<p:processor name="oxf:xinclude">
		<p:input name="config">
			<delegation:execute service="ca-traffic" operation="getTraffic" xmlns:delegation="http://orbeon.org/oxf/xml/delegation">
				<xi:include href="input:xslt-result"/>
			</delegation:execute>
		</p:input>
		<p:input name="xslt-result" href="#xslt-result"/>
		<p:output name="data" id="web-service-call"/>
	</p:processor>
	
	<p:processor name="oxf:delegation">
		<p:input name="interface">
			<config>
				<service id="ca-traffic" type="webservice" endpoint="http://s121212121212dfdfervices.xmethods.net/soap/servlet/rpcrouter">
					<operation nsuri="urn:xmethods-CATraffic" name="getTraffic"/>
				</service>
			</config>
		</p:input>
		<p:input name="call" href="#web-service-call"/>
		<p:output name="data" id="web-service-result" debug="true"/>
	</p:processor>
	
    <p:processor name="oxf:xslt">
        <p:input name="data" href="#web-service-call"/>
        <p:input name="config">
            <xsl:stylesheet version="2.0">
                <xsl:import href="oxf:/oxf/xslt/utils/copy.xsl"/>
                <xsl:template match="/">
                    <xsl:copy-of select="." copy-namespaces="no"/>
                </xsl:template>
            </xsl:stylesheet>
        </p:input>
        <p:output name="data" ref="data"/>
    </p:processor>	

</p:config>

  

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Hi Adrian,

You are saying the you where running this pipeline but you were not
reading its "data" output? As you discovered, if you don't read that
output, all the processor required to produce that data just won't
run, as that data is not needed.

I understand that this can be confusing, but this behavior is really
core to the "essence" of pipelines. The execution of a pipeline is not
procedural, but is data-driven. The "need" for data drives the
execution of processors.

Alex

On 4/10/07, Adrian Baker [hidden email] wrote:

 Ok, so glancing through this thread
(http://mail-archive.objectweb.org/ops-users/2005-01/msg00319.html)
it seems I have to connect the output of the processor in question to the
null serializer, to ensure it's executed. Perhaps this should be in the FAQ
somewhere (I looked there but saw nothing)?

 Can I just mention this seems very arcane? We're aiming to provide hooks in
our application for implementers to connect snippets of XPL to, to allow
them to do their own integration. XPL will already be a bit of a learning
curve for them, but just by following an example of tying together some
inputs, an XSLT & a web service they can achieve a lot without being XPL
experts. Requiring somewhat unintuitive steps like this makes it harder.
When we're just using small bits of XPL as glue code metaphors like pipes &
circuits are pretty obscure: the XPL pipeline is just a simple series of
procedural steps, and it's confusing when it doesn't behave this way.

 Adrian

 Adrian Baker wrote:
 I've got a pipeline which has no outputs, only inputs. I've been having
trouble getting it to run: nothing seems to happen, even with debug
attributes throughout nothing is logged.

 I'm using the Java API to execute & read output from the pipeline.

 I've found that processors which aren't eventually connected to outputs of
the pipeline *which are then read* aren't seeming to get executed. For
example, in the attached pipeline the delegation processor should throw an
error because the address isn't invalid: instead, the delegation processor
seems to get skipped altogether & the pipeline runs ok.

 If you modify the final xslt processor to use the web-service-result
document as an input (instead of web-service-call), then the delegation
process is run, and you get the expected error. This seems totally wrong!

 Adrian

______________________________________________________________________
 This email has been scanned by the MessageLabs Email Security System.
 For more information please visit
http://www.messagelabs.com/email
______________________________________________________________________
 ________________________________

<?xml version="1.0"?>
<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
 xmlns:oxf="http://www.orbeon.com/oxf/processors"
 xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 xmlns:xi="http://www.w3.org/2001/XInclude"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

 <p:param type="output" name="data" />
 <p:param type="input" name="data"/>

 <p:processor name="oxf:xslt">
 <p:input name="data" href="#data"/>
 <p:input name="config">
 <hwynums xsl:version="2.0">
 <xsl:value-of select="/parameters/highway"/>
 </hwynums>
 </p:input>
 <p:output name="data" id="xslt-result"/>
 </p:processor>

 <p:processor name="oxf:xinclude">
 <p:input name="config">
 <delegation:execute service="ca-traffic" operation="getTraffic"
xmlns:delegation="http://orbeon.org/oxf/xml/delegation">
 <xi:include href="input:xslt-result"/>
 </delegation:execute>
 </p:input>
 <p:input name="xslt-result" href="#xslt-result"/>
 <p:output name="data" id="web-service-call"/>
 </p:processor>

 <p:processor name="oxf:delegation">
 <p:input name="interface">
 <config>
 <service id="ca-traffic" type="webservice"
endpoint="http://s121212121212dfdfervices.xmethods.net/soap/servlet/rpcrouter">
 <operation nsuri="urn:xmethods-CATraffic" name="getTraffic"/>
 </service>
 </config>
 </p:input>
 <p:input name="call" href="#web-service-call"/>
 <p:output name="data" id="web-service-result" debug="true"/>
 </p:processor>

 <p:processor name="oxf:xslt">
 <p:input name="data" href="#web-service-call"/>
 <p:input name="config">
 <xsl:stylesheet version="2.0">
 <xsl:import href="oxf:/oxf/xslt/utils/copy.xsl"/>
 <xsl:template match="/">
 <xsl:copy-of select="." copy-namespaces="no"/>
 </xsl:template>
 </xsl:stylesheet>
 </p:input>
 <p:output name="data" ref="data"/>
 </p:processor>

</p:config>


 ________________________________


--
You receive this message as a subscriber of the [hidden email]
mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws