SLD Validator uses apache xerces classes
Description
Environment
Activity
codehaus April 10, 2015 at 4:11 PM
CodeHaus Comment From: bowens - Time: Wed, 3 May 2006 01:49:14 -0500
---------------------
<p>I just committed the build.xml file and it has the change in it.</p>
codehaus April 10, 2015 at 4:11 PM
CodeHaus Comment From: cholmes - Time: Tue, 2 May 2006 09:54:19 -0500
---------------------
<p>Could you attach the war that has these two jars in it? </p>
<p>I just did an update on svn and did 'ant release-war', and I definitely didn't see any xercesImpl.jar. Maybe I'm doing something wrong? Looking at the commit list I don't see any xerces updates since 1.3.0...</p>
codehaus April 10, 2015 at 4:11 PM
CodeHaus Comment From: bowens - Time: Tue, 2 May 2006 01:29:55 -0500
---------------------
<p>I think the jars got added there a while back. The two jars are in the war in WEB-INF/lib, and in the binary distro.</p>
codehaus April 10, 2015 at 4:11 PM
CodeHaus Comment From: cholmes - Time: Thu, 30 Mar 2006 12:55:50 -0600
---------------------
<p>Upped the priority, since there have been several reports on this, we rely on the presence of xerces in both the SLDValidator and in wfs-insert it appears. This isn't a problem in the binary releases, but is for the .war. So we just need to build the war with the xerces stuff. Hopefully so we're not replicating the jars in two locations (they may be necessary for the jetty start-up, or I'd say we'd just move them all to the WEB-INF/lib)</p>
codehaus April 10, 2015 at 4:11 PM
CodeHaus Comment From: cholmes - Time: Wed, 22 Feb 2006 17:48:15 -0600
---------------------
<p>Ok, from the user:
I have deployed geoserver1.3 war on tomcat5.5 and i am having
jdk1.5_06 . I could resolve the error after adding the xercesImpl and
xml-api jars . My Sld was very bacis and i have checked for compliance
against the schema .</p>
<p>But after that i never again got the errror again.
—</p>
<p>So I guess we should consider including them in the WEB-INF/lib section? Ideally just for the war, since they're already in the binary releases.</p>
In an email from a user: http://www.nabble.com/error-while-creating-new-style-.-t1144654.html - http://www.nabble.com/error-while-creating-new-style-.-t1144654.html we have a report of classdef not found. Most jvms include xerces, but we can not rely on it, it seems. The cleaner choice is to use all Java api's for parsing, which I believe is how this should have been coded, since there is no justificatio nfor not using the standard apis in the code. If we have to use the xerces SAXParser then we should explain why in the code, and include the jar in our distribution.