Comments on: JSTL 1.2 and “Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found” exception http://www.mooreds.com/wordpress/archives/476 Tue, 07 Feb 2012 14:11:43 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jonathan http://www.mooreds.com/wordpress/archives/476/comment-page-1#comment-2304 Jonathan Wed, 22 Oct 2008 23:08:14 +0000 http://www.mooreds.com/wordpress/archives/000476#comment-2304 Terrific, this works great with my latest web application, but it's actually under ServletExec 6.0 (not Tomcat). I was getting a "No provider found for SAXParserFactory" error when the JSTL core validator was trying to run. This is a real problem because multiple web applications all tend to run within the same JVM, so any static or system property changes affect all web applications. Terrific, this works great with my latest web application, but it’s actually under ServletExec 6.0 (not Tomcat). I was getting a “No provider found for SAXParserFactory” error when the JSTL core validator was trying to run.

This is a real problem because multiple web applications all tend to run within the same JVM, so any static or system property changes affect all web applications.

]]> By: mark http://www.mooreds.com/wordpress/archives/476/comment-page-1#comment-2247 mark Thu, 19 Jun 2008 21:35:11 +0000 http://www.mooreds.com/wordpress/archives/000476#comment-2247 You can sometimes get around these problems defining the javax.xml.parsers.SAXParserFactory implementation class in the services directory inside you jar file META-INF/services/javax.xml.parsers.SAXParserFactory If you put the implementation bundled with the JVM running a main method with a javax.xml.parsers.SAXParserFactoy.newInstance().getClass().getName(), will let you know what that is. You can sometimes get around these problems defining the javax.xml.parsers.SAXParserFactory implementation class in the services directory inside you jar file

META-INF/services/javax.xml.parsers.SAXParserFactory

If you put the implementation bundled with the JVM running a main method with a javax.xml.parsers.SAXParserFactoy.newInstance().getClass().getName(), will let you know what that is.

]]>