This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Xalan 2.0 compatibility problems
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] Xalan 2.0 compatibility problems
- From: "Nick Ridout" <costempd at us dot ibm dot com>
- Date: Wed, 28 Feb 2001 16:39:33 -0500
- Reply-To: xsl-list at lists dot mulberrytech dot com
I got the same error and have backed off to older versions of Xerces/Xalan.
If no-one answers here and you find an answer somewhere else, please post
the answer and/or send me an email. Thanks!
Nick Ridout
consulting@ridout.net
costempd@us.ibm.com
>Date: Tue, 27 Feb 2001 21:35:09 -0500
>From: Kumar Shailendra <Kumar.Shailendra@msdw.com>
>Subject: [xsl] Xalan 2.0 compatibility problems
>Hi,
>I am trying to run xalan1.2.0 compliant code with xalan 2.0. I have put
>xalanj1compat.jar in the classpath before xalan2.0.
>My program compiles fine with the new xalan but gives runtime error at
>XSLTProcessorFactory.getProcessor(); method call.
>The error message I get is
>SystemId Unknown; Line 0; Column 0;
>javax.xml.transform.TransformerException: SAX Exception.
>
>Am I doing something wrong or do I need to do some setup that I haven't
>done?
>
>Secondly can a xalan1.2.x & xalan2.0 complaint application coexist in
>the same environment? Those applications use different versions
>of xerces.And we found that all the versions of xerces have same
>directory structure.Wouldn't it create conflict?
>
>Thanks,
>Shailendra
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list