xerces jar name changes behaviour

Asked Mar 11 '19 at 23:16

Active Mar 11 '19 at 23:51

Viewed 66 times

I have an older application that uses a jar named xerces.jar. Looking at this I can see that it is the same as xercesImpl-2.9.1.jar from the maven repository.

When I run the application the xml validation behaves differently depending on if the jar is named xerces.jar or xercesImpl-2.9.1.jar.

I suspect there is something going on with the order that it it found on the classpath but I don't fully understand what is going on.

Any ideas as to what is going on?

The particular change is this: The start tag looks like:

<Message xmlns="http://www.foo.com/messaging" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" release="006" version="010" xsi:schemaLocation="file:///C:/SOME/PATH">

When the jar is named "xerces.jar" this accepted when the app validates against a specific schema. When the jar is named "xercesImpl-2.9.1.jar" then it gives the error: Attribute 'xsi:schemaLocation' is not allowed to appear in element

edited Mar 11 '19 at 23:51

asked Mar 11 '19 at 23:16

Dave

13,518
7
42
51

Perhaps "xerces.jar" is not actually the same as "xercesImpl-2.9.1.jar" – Andreas Mar 11 '19 at 23:25
Which behaviour is correct? – user207421 Mar 11 '19 at 23:34
The jars are the same except for whitespace in some files. Also, if I rename xercesImpl-2.9.1.jar the behaviour changes. – Dave Mar 11 '19 at 23:44
@user207421 - I'm not sure which is correct. – Dave Mar 11 '19 at 23:44
1

Smells like, https://stackoverflow.com/questions/11677572/dealing-with-xerces-hell-in-java-maven – Darren Forsythe Mar 11 '19 at 23:54

xerces jar name changes behaviour

0 Answers0