SLD Validator uses apache xerces classes
----------------------------------------
Key: GEOS-546
URL: http://jira.codehaus.org/browse/GEOS-546
Project: GeoServer
Type: Bug
Versions: 1.3.0
Reporter: Chris Holmes
Assigned to: dblasby
Fix For: 1.4.M1, 1.3.1
In an email from a user: 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[ http://jira.codehaus.org/browse/GEOS-546?page=all ]
Chris Holmes reopened GEOS-546:
-------------------------------
Could you attach the war that has these two jars in it?
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...
SLD Validator uses apache xerces classes
----------------------------------------
Key: GEOS-546
URL: http://jira.codehaus.org/browse/GEOS-546
Project: GeoServer
Type: Bug
Versions: 1.3.0
Reporter: Chris Holmes
Assignee: Brent Owens
Priority: Critical
Fix For: 1.4.M1, 1.3.1
In an email from a user: 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
I didn't commit the build file yet. I will commit it this morning.
Brent Owens
(The Open Planning Project)
Chris Holmes (JIRA) wrote:
[ http://jira.codehaus.org/browse/GEOS-546?page=all ]
Chris Holmes reopened GEOS-546:
-------------------------------
Could you attach the war that has these two jars in it?
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...
SLD Validator uses apache xerces classes
----------------------------------------
Key: GEOS-546
URL: http://jira.codehaus.org/browse/GEOS-546
Project: GeoServer
Type: Bug
Versions: 1.3.0
Reporter: Chris Holmes
Assignee: Brent Owens
Priority: Critical
Fix For: 1.4.M1, 1.3.1
In an email from a user: 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.