Warning : Current XML parsers seems to not support EntityResolver2

General Discussion
1

Hi all,

May be this has already been discussed, but I didn’t find any reference.
Should I worry about this warning message :
liquibase: Current XML parsers seems to not support EntityResolver2. External entities won’t be correctly loaded

And how can I solve it ?

Best regards,
Xavier.

2

It was reported by someone else.  I looked into it a bit and didn’t see a solution off hand.  I didn’t know how much it was used since there is the tag which is generally preferable, but I can look into it more.

It worked for you in 1.9?

Nathan

3

Didn’t try 1.9.

I solved the warning by removing an xerces implementation and using the JRE 1.6 provided one.

4

I know this is an old topic but I am getting the same warnings and I can’t figure out how to stop them. Our clients logs are getting flooded with these messages when starting up their servers.

I threw a break point in the method that outputs this message. Here is the xsd files it is throwing these errors on:

http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/security/spring-security-3.1.xsd
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.springframework.org/schema/tool/spring-tool-3.0.xsd
http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
http://www.springframework.org/schema/task/spring-task-3.0.xsd

Any ideas?

We are using liquibase 2.0.1

5

Same here using liquibase 2.0.3. Any ideas yet?

6

We have the same issues.

The root problem is going to be (as one poster mentioned above) the inclusion of another XML parser in the classpath.  In our case, this is due to some eager library roping in Xerces or Xalan or one of their dependencies (I have spent huge portions of my career fighting these libraries and just now assume that if I see them within about 100 feet of my deployment unit something is going to break).  I have not had the time in our case to see exactly which one of these causes their XML parser to be used instead of the built-in JDK one.

Best,
Laird

–
http://about.me/lairdnelson