Forum Discussion
SmartBear_Suppo
Alumni
17 years agoHi Li,
FYI, this problem is not specific to soapUI.
My guess is that the problem is caused by the mismatching XSLT version supported by Ant JUnit plugin (which contains XSLT files that are XSTL 1.0, as you correctly noted) and XSLT processor (supporting XSLT version 2.0). My guess #2 is that you have the newer XSLT processor (like Saxon) somewhere in classpath so that it's loaded before some other XSLT processor (like Xalan which implements XSLT v1.0). For further troubleshooting I would suggest googing it out.
Good luck!
Cheers!
/Nenad Nikolic a.k.a. Shonzilla
FYI, this problem is not specific to soapUI.
My guess is that the problem is caused by the mismatching XSLT version supported by Ant JUnit plugin (which contains XSLT files that are XSTL 1.0, as you correctly noted) and XSLT processor (supporting XSLT version 2.0). My guess #2 is that you have the newer XSLT processor (like Saxon) somewhere in classpath so that it's loaded before some other XSLT processor (like Xalan which implements XSLT v1.0). For further troubleshooting I would suggest googing it out.
Good luck!

Cheers!
/Nenad Nikolic a.k.a. Shonzilla