Problem with pipeline processor

I have a strange problem invoking an .xpl file which creates a dynamic pipeline and then in turn invokes that.

Without any debug attributes, the pipeline throws an exception:

11:19:45,031 [TeeProcessor] creation
org.orbeon.oxf.common.ValidationException: null, line 0, column 0:
null, line 0, column 0:

at org.orbeon.oxf.processor.pipeline.TeeProcessor.(TeeProcessor.java:45) at org.orbeon.oxf.processor.pipeline.PipelineBlock.connectProcessorToHref(PipelineBlock.java:96) at org.orbeon.oxf.processor.pipeline.PipelineBlock.connectProcessorToHref(PipelineBlock.java:190) at org.orbeon.oxf.processor.pipeline.PipelineProcessor.createConfigFromAST(PipelineProcessor.java:271) at org.orbeon.oxf.processor.pipeline.PipelineProcessor.readPipelineConfig(PipelineProcessor.java:470) at org.orbeon.oxf.processor.pipeline.PipelineProcessor.access$2200(PipelineProcessor.java:66) at org.orbeon.oxf.processor.pipeline.PipelineProcessor$9.read(PipelineProcessor.java:626) at org.orbeon.oxf.processor.ProcessorImpl.readCacheInputAsObject(ProcessorImpl.java:470) at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:622) at org.orbeon.oxf.processor.pipeline.PipelineProcessor$1.getInput(PipelineProcessor.java:140) at org.orbeon.oxf.processor.pipeline.PipelineProcessor$1.readImpl(PipelineProcessor.java:89) at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)

The problem goes away if I put a debug=”true” attribute on a particular element in the dynamically constructed pipeline.

I’ve attached 3 files:

–        Working xpl file (with comment concerning where to put single debug=”true” hack), which constructs a dynamic
pipeline to perform an XML include of one file into another.

–        Two XML files that are passed to the pipeline, one constituting the master XML that performs the inclusion, and
the other constituting the XML to be included.

(In this particular example there is no need for a dynamically constructed pipeline, but this is a simplified version of more
elaborate example where the number of XML include’s in the master file is unbounded at runtime.)

My guess is that adding “debug” subtly influences the flow of control of the pipeline, and is hiding the underlying issue.

Thanks

Alan