Although it seems I'm wrong, that's just the XSLTC in a separate jar, not XSLT.
On Fri, Sep 5, 2008 at 12:04 AM, jason marshall <[EMAIL PROTECTED]> wrote: > I looked at this recently, and discovered that there's two Xalan jar > files available now, one with XSLT and one without. Since I only > needed XPath, we looked at going that route (but decided not to update > our libraries, alas). In the end it was only going to save me 800K of > library, and cost me a full regression cycle, so we opted to stick > with what we had. > > I ran my unit tests over it and it seemed to run okay. Didn't get much > beyond that though. > > -Jason > > On Thu, Sep 4, 2008 at 10:18 PM, Clive Brettingham-Moore > <[EMAIL PROTECTED]> wrote: >> Sounds like a lot of work. >> I think XML sec picks up Xalan classes directly (not via service/factory >> lookup), so you should be able to just remove the >> META-INF/services/javax.xml... entries from the xalan jar and the app server >> won't even notice that it is an XSLT provider. >> >> > > > > -- > - Jason > -- - Jason
