cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hunsberger, Peter" <Peter.Hunsber...@stjude.org>
Subject RE: XML input module (was: RE: Nice changes!)
Date Fri, 04 Oct 2002 16:33:50 GMT
> > 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.

That would work, but where I'm heading I essentially want the equivalent of
a uri-resolver to be coded using XSLT looking not only at the URI but also
the current context.  I've generated a reply back to Christian that gives a
bit of a sketch of what such a thing might look like.

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


Mime
View raw message