• To: "'Robert Koberg'" <rob@k...>
• Subject: RE: Seeking Examples of XSLT Memory Stress
• From: "Michael Kay" <mike@s...>
• Date: Wed, 17 Aug 2005 17:09:26 +0100
• Cc: "'Alan Gutierrez'" <alan-xml-dev@e...>,<xml-dev@l...>
• In-reply-to: <43035B5E.6050501@k...>
• Thread-index: AcWjQo2sYphiIBiwQBi1loSk2IpWEgAAnEbw

> 
> 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.
> 
> 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/

• References:
  • Re: Seeking Examples of XSLT Memory Stress
    • From: Robert Koberg <rob@k...>

• Prev by Date: Re: Seeking Examples of XSLT Memory Stress
• Next by Date: Re: Seeking Examples of XSLT Memory Stress
• Previous by thread: Re: Seeking Examples of XSLT Memory Stress
• Next by thread: Re: Seeking Examples of XSLT Memory Stress
• Index(es):
  • Date
  • Thread