Andrew Timberlake wrote:
Could I turn the handle the URIResolver specificaly for certain
Transformers or would any changes effect the entire cocoon application?
In Cocoon the transformer's URIResolver is already used by
Cocoon's own resolver, and AFAIK there is no easy way to
hook in there.
Certain extension elements and functions already provided by
the XSLT processor are also a concern, in Saxon you can turn
them off summarily by a configuration setting.
Again, would this end up being application wide or could you deal with
this for on Transformer only.
This can be handled by a slightly hacked XSLTTransformer
which can be used side-by-side with unmodified transformers,
the same way you can use multiple serializers and parsers
in your application.
But who needs XSLT extensions anyway? :-)
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
