Repost [HELP!] Incomplete pipeline in

[Jan Hoskens <jh...@schaubroeck.be>]

HELP!

Still no succes with the latest cvs version of cocoon! When changing back to release 2.1.3, all is fine (flow does show form), but then I don't have all the new woody stuff (union, fixes, ...)! When using the latest version in cvs, still gives the error described below! (error when aggregating)
  ----- Original Message ----- 
  From: Jan Hoskens 
  To: users@cocoon.apache.org 
  Sent: Thursday, January 15, 2004 9:12 AM
  Subject: Incomplete pipeline in <map:aggregate>


  Hi, 

  I just changed my setup from the cocoon release 2.1.3 to a cvs head(checked out yesterday). When I tested my site, it keeps giving me an error when I call a flow (currently still apples) and it wants to show the display-pipeline. Well, it gets through the pipeline but when the result should be aggregated, it fails:

  ERROR   (2004-01-15) 08:40.23:726   [sitemap.handled-errors] (/cocoon/cocoontest/Samples/Lonen/Besturen/0459/Vb_1_2_1_02_2004/HD15/DE%20ZEE%20NYNKE-22.xml) http8080-Processor4/PipelineNode: Failed to execute pipeline.
  org.apache.cocoon.ProcessingException: Failed to execute pipeline.: org.apache.cocoon.ProcessingException: Attempted to process incomplete pipeline.
   at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processXMLPipeline(AbstractProcessingPipeline.java:564)
   at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:196)

  All my pages go through this resource (left some other parts out for debugging, otherwise it would be stupid to use aggregation;-):

  <map:resource name="AggregatedPage">
     <map:aggregate element="Document">
      <map:part src="cocoon:/{page-uri}" strip-root="true"/>
     </map:aggregate>
     <map:serialize type="xml"/>
  </map:resource>

  The strange thing is that it all used to work with the previous version (release 2.1.3), and it also works fine if I use a simple redirect to the flow:

  <map:resource name="AggregatedPage">
     <map:redirect-to uri="cocoon:/{page-uri}"/>
  </map:resource>

  my display-pipeline:

   <map:match pattern="Samples/*-display-pipeline">
        <!-- pipeline to show the form -->
        <map:generate type="serverpages" src="woody/Example2-template.xsp">
         <map:parameter name="rootdir" value="{1}"/>
        </map:generate>
        <map:transform type="cinclude"/>
        <map:transform type="woody"/>
        <map:transform src="stylesheets/woody-samples-styling.xsl"/>
        <map:serialize type="xml"/>
  </map:match> 

  I think the error states itself when the aggregation happens after the display-pipeline has ended, because I get the following log sequences:(watching the timestamp)

  <sitemap log>
  DEBUG   (2004-01-15) 08:40.23:726   [sitemap] (/cocoon/cocoontest/Samples/Lonen/Besturen/0459/Vb_1_2_1_02_2004/HD15/DE%20ZEE%20NYNKE-22.xml) http8080-Processor4/ContentAggregator: Generating aggregated content
  INFO    (2004-01-15) 08:40.23:766   [sitemap] (/cocoon/cocoontest/Samples/Lonen/Besturen/0459/Vb_1_2_1_02_2004/HD15/DE%20ZEE%20NYNKE-22.xml) http8080-
  Processor4/HandleErrorsNode: Processing handle-errors at file:/d:/cocoontest/sitemap.xmap:782:23
  <handled errors, copy from above>
  ERROR   (2004-01-15) 08:40.23:726

  Any ideas why this Error pops-up?

  Bye,

  Jan