Return-Path: 
 <cocoon-dev-return-23375-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 11897 invoked by uid 500); 27 Feb 2002 12:54:50 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 11884 invoked from network); 27 Feb 2002 12:54:50 -0000
Message-ID: <20020227125451.39052.qmail@web14606.mail.yahoo.com>
Date: Wed, 27 Feb 2002 04:54:51 -0800 (PST)
From: James Burton <strangegames@yahoo.com>
Reply-To: strangegames@yahoo.com
Subject: RE: XML-Based Selection (Redirect Serializer?)
To: cocoon-dev@xml.apache.org
In-Reply-To: <MLEAJJEAAELCMLAIJNFIAEAGDIAA.mlangham@sundn.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi Matthew,

Thanks very much for the suggestion.  It works in
theory (at least I am able to switch to a different
pipe based on different XML from the stream), but has
two problems:

1) If possible, I'd like to keep the mapping from XML
result => new pipeline inside of the sitemap file.

2) I get an error with CInclude "ProcessingException:
Failed to execute pipeline.:
org.apache.cocoon.ProcessingException: Attempted to
process incomplete pipeline" every *alternate* time I
reload the page.  I am using these pipes

 <!-- Generate request XML as the "get-req" pipe -->
 <map:match pattern="get-req" >
   <map:generate type="request" />
   <map:serialize type="xml" />
 </map:match>

 <!-- Include "get-req" into an XML file -->    
 <map:match pattern="cinclude-test" >
   <map:generate src="a.xml" />
   <map:transform type="cinclude" />
   <map:serialize type="xml" />
 </map:match>

With this data for "a.xml":

<?xml version="1.0" encoding="UTF-8"?>
<page
xmlns:cinclude="http://apache.org/cocoon/include/1.0">
  <title>Hello</title>
  <content>
    <para>This will test cinclude</para>
    <cinclude:include src="cocoon:/get-req"
                      element="included"/>
  </content>
</page>

Could this be some sort of multithreading error causes
by CInclude not being used to "cocoon:/"-type URLs?

So here is my next question: it looks like the core
lines in the CIncludeTransformer are these:

    source = this.sourceResolver.resolve(src);
    source.toSAX(consumer);

Does this mean that all it would take to generate a
SAX stream from the pipeline "foo" would be to execute
the code

  this.sourceResolver.resolve("cocoon://foo");
  source.toSAX(...)

And how does that work if the pipe invoked returns
non-XML content?  Actually, it seems easier if someone
could tell me the code for invoking and outputting an
arbitrary Cocoon URI (so I could make the custom
serializer), but I have no idea how to do that.

Thanks,
Jim

--- Matthew Langham <mlangham@s-und-n.de> wrote:
> Hi James,
> 
> one solution that may help:
> 
> Your Transformer -> Stylesheet ->
> CIncludeTransformer -> serializer
> 							:
>  							v
> 						pipeline (via: "cocoon://...")
> 
> So the stylesheet constructs the URI from the data
> your transformer sends.
> 
> Matthew


__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org