Hi,

> -----Original Message-----
> From: Christian Haul [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 04, 2002 12:57 AM
> To: [EMAIL PROTECTED]
> Subject: Re: XML input module (was: RE: Nice changes!)
>
>
> On 02.Oct.2002 -- 09:47 AM, Hunsberger, Peter wrote:
> > This is likely an issue you're going to run into also; mapping XPath to
> > random session objects might be possible, but I suspect the two domains
> > aren't perfectly isomorphic :-(
>
> Yes, but since we don't need to work on strings, less so. All these
> modules work on Objects and only on some occasions you really want
> strings. In the sitemap for example.
>
> [a highly interesting discussion snipped]
>
> > No more matchers, no more selectors; just XSLT templates ;-)...  Seriously,
> > once (if?) XSLT 2 gains regex capabilities I can't really see why a pure
> > XSLT pipeline couldn't do everything that matchers and selectors do, therby
> > eliminating huge chunks of the current Cocoon code base?
>
> Maybe, maybe not. One would need to use a lot extension functions to
> achieve similar things (e.g. j2ee, databases and stuff) but that might
> be portable to other pipeline systems (?). OTOH Apache Cocoon a lot
> about SoC and it will need to be seen if that works as well with your
> suggested approach.

Instead of extensions you could use custom URIResolvers to return the result
from anywhere (or just do something and return succes/fail) to an representation
usable by a transformation.

The separation occurs in the resolver which can be configured to handle your
particular needs.

best,
-Rob


>
> I believe, many would be interested in your approach. I hope you find
> the time to work on it.
>
>       Chris.
> --
> C h r i s t i a n       H a u l
> [EMAIL PROTECTED]
>     fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to