Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Conal Tuohy" <conalt@paradise.net.nz>
To: <cocoon-dev@xml.apache.org>
Subject: RE: Flow wishlist :)
Date: Tue, 3 Dec 2002 08:15:51 +1300
Message-ID: <001801c29a37$3b27fb70$d9784fcb@insurgentes.local>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <601F6322AD71D5118D6C0003472515290660D093@sjmemexc1.stjude.org>

Hi Peter

Peter wrote:
> >> Hmm, I guess I've been exploring this long enough that I
> thought it
> >> was somewhat intuitively obvious, sorry...  (Someone has
> also remarked
> > that this sounded somewhat like a capability that was in C1.)
> >

Stefano(?) wrote:
> > yeah, you could implement what you want using dynamically added PI
> > (processing instructions) for the C1 reactor, but it would
> end up being
> > very messy anyway.
>
> When it was described to me it didn't really sound like what
> I wanted...

I think Stefano is on the right track with this dynamic PI pattern ... but
since I never used C1 I've only got a theoretical notion of the C1
"reactor". But I've used a similar pattern in C2, I think. You can use a
pipeline (or a small number of pipelines) containing an XSLT transformer
followed by an include transformer. The XSLT transform can make your
decision, and insert elements like this:
<xi:include href="cocoon://{$result-of-some-complex-functional-logic}"/>
Then the include transformer resolves the url and recursively calls the
sitemap. The URL could resolve to a database query result, or an error 500
page. This gives you quite a functional "style" where you need it. One issue
I'm aware of here is the "cacheability" of the include transformer, but this
may not be an issue which your search results anyway.

Cheers

Con


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