> I've been poking through the source, to better understand the innards
> of eXist. I can't seem to find, however, any classes for XSL
> Translation. There's one for XQuery, one for XPath... but not XSL. Can
> anyone give me an overview of how XSL is applied when requesting files?
If you're looking for the XQuery function , it's in :
Jean-Marc Vanel 01 39 43 31 46
Conseil et Services / développement & intégration logiciels
Logiciel libre, Web, Java, XML ...
A la pointe de la technique, au service des projets
http://jmvanel.free.fr/ ===) CV, software resources
> I've been poking through the source, to better understand the innards of
> eXist. I can't seem to find, however, any classes for XSL Translation.
> There's one for XQuery, one for XPath... but not XSL. Can anyone give me
> an overview of how XSL is applied when requesting files?
eXist doesn't implement its own XSL engine (that would certainly be possible,
but we already have enough problems to make our XQuery and XPath engines
standards compliant ;-). Instead, eXist uses the XSL processor supplied by
Java and just takes care to cache stylesheets etc. Where this is done depends
on the interface you use: Jean-Marc already mentioned the transform:transform
function, which supports caching. If you just apply an XSL to a document via
the REST service, the XSL is compiled on-the-fly and applied by class
org.exist.storage.serializers.Serializer, method setStylesheet(). No caching
takes place here.
In the future, both implementations should be merged into a common base, so
they can both benefit from caching etc.