RE: javax.xml.transform: prohibiting Java extensions

> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Michael Kay
> Sent: Friday, May 25, 2001 11:53 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  javax.xml.transform: prohibiting Java extensions
>
>
> > I am considering to use XPath as a query language within a WebDAV DASL
> > grammar. This means client software can submit a query where
> > the condition
> > is expressed as XPath expression applied to the WebDAV
> > properties of the resource(s).
>
> An interesting thing to do (count me as interested too). Of course, to do
> this you must first define a mapping from the WebDAV data model
> to the XPath
> data model, then you must somehow arrange for your chosen XPath engine to
> connect to this data model.

Well, for now I chose the naive approach -- build the <DAV:response> element
for a particular resource, then apply a simple transformation to it (which
will just test whether the XPath expression on the children will match).

> > Obviously, one needs a way to prohibit execution of extension
> > functions...
>
> A good point, I don't know an obvious answer.

I'd say that an XSLT engine that does support Java extensions should offer a
way to switch this feature off (maybe by package or class).


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list