Michael Kay wrote:
>>I did not know that and it is good to know. I disable extensions (and
>>don't really investigate them) as I run some untrusted XSLs in my CMS
>>webapp. I wonder, is there some way to configure Saxon to allow this
>>extension, but not allow any others?
>
>
> You can define a subclass of JavaExtensionLibrary and nominate this using
> configuration.setExtensionBinder(); in your subclass you can override the
> bind() method to select which extension functions you want to allow through.
That is perfect! It will really take a load of the servers. Now I need
to find out what other extensions I have been missing all these years.
thanks,
-Rob
>
>>Any chance of this type of thing getting into the spec?
>>
>
>
> I doubt it - too hard to specify the semantics.
>
> Michael Kay
> http://www.saxonica.com/
>
>
