According to the docs, trax.Processor can pick up "plugged" Processors using System Properties.
(like org.xml.trax.Processor.xslt should point to the factory that can instantiate an XSLT
Processor). More info at http://xml.apache.org/xalan-j/apidocs/trax/Processor.html
Is this good enough for moving forward?
Thanks,
dims
--- Nicola Ken Barozzi <nicolaken@supereva.it> wrote:
>
> ----- Original Message -----
> From: "Davanum Srinivas" <dims@yahoo.com>
> To: <cocoon-dev@xml.apache.org>; <Giacomo.Pati@pwr.ch>
> Sent: Monday, October 02, 2000 1:40 PM
> Subject: Re: [C2] Short TODO list [was CLI almost there]
>
>
> > > > Is there anyone that wants to help replacing Xalan1 with Xalan2 using
> > > > the TRaX interfaces?
> > >
> > > +100000
> >
> > Does this mean just replacing XSLTProcessor with trax.Processor? anything
> else?
>
> No, unfortunately things go much deeper, that is just the tip of the
> iceberg.
> The problem is that extensions are used and Xalan2 is not up to snuff,
> AFAIK, but mostly the ting is that Xalan support was hardcoded.
> I agree with Stefano, that XSL use in C2 code should be pluggable.
>
> nicola_ken
>
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/
|