list4xt : Mailing list for the XT users community.
[list4xt] Re: saxon:evaluate
Subject: [list4xt] Re: saxon:evaluate
User: Website From: Paul Tchistopolskii (pault12@pacbell.net)
Date: 29/08/2000 - 10:08
Eric,
> Just a couple of thoughts about the necessity of the filename
> trickery...
>
> Basically, I don't understand why you can't set this parser only for
> this purpose, avoiding testing for the filename.
Because the same parser should is used to process legal
XSL . <xsl:include and all that stuff.
> If you are working at a text level, parsing a stylesheet stored
> somewhere as a text, can't you use an EntityResolver instead ?
>
> If your HackedXMLParser sends SAX events generated from variables or
> context, couldn't you just install it through "setParser" without
> needing any trickery on the name ?
The answer is "in simple case: yes. But not always".
> Eric (confused)
>
> your HackedXMLParser will send SAX events
Yes. Maybe there is a better way to do this all.
As I already wrote here, there are some not
obvious places. For example, xt:document
is broken by design in SAX mode. I mean not
everything in XT has been tested in SAX mode.
Ux makes preprocessing of XSLScript, sandbox
( /etc/file becomes /tomcat/blabla/etc ) ,
document( '!/ pipe | here ') and whatever else -
using just one function ( parse() ) of
HackedXMLParser I don't see any better
way.
Rgds.Paul.
--
Mailing list for the XT users community. (http://advantagehomerates.com)
(mailto:list4xt-request@4xt.org?Subject=unsubscribe to unsubscribe)
Archive générée par hypermail 2b28 le 06/11/2001 - 11:46 CET
webmaster@4xt.org
|