Yes there is a reason for it, unpatched xerses has problems in modular classloader environment.

see for our changes here.

Maybe new version of xerses includes fixes for what we already have but if they don't,
we should just take their code and apply our fixes on top of it and release our patched version of 2.11.

If you are up for it, check our changes and see if how stuff is now done in upstream.

On Thu, Aug 7, 2014 at 11:29 PM, Alessio Soldano <> wrote:
is there a specific reason for WildFly to consume (a patched version of)
Xerces 2.9.1 and not move to the latest release (2.11.0) ? Release notes
at .

Alessio Soldano
Web Service Lead, JBoss

wildfly-dev mailing list