<div dir="ltr"><div><div>Yes there is a reason for it, unpatched xerses has problems in modular classloader environment.<br><br>see <a href="https://github.com/jboss/xerces/commits/Xerces-J_2_9_1_jbossas">https://github.com/jboss/xerces/commits/Xerces-J_2_9_1_jbossas</a> for our changes here.<br>
<br></div>Maybe new version of xerses includes fixes for what we already have but if they don't, <br>we should just take their code and apply our fixes on top of it and release our patched version of 2.11.<br><br></div>
<div>If you are up for it, check our changes and see if how stuff is now done in upstream.<br></div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 7, 2014 at 11:29 PM, Alessio Soldano <span dir="ltr"><<a href="mailto:asoldano@redhat.com" target="_blank">asoldano@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<br>
is there a specific reason for WildFly to consume (a patched version of)<br>
Xerces 2.9.1 and not move to the latest release (2.11.0) ? Release notes<br>
at <a href="http://xerces.apache.org/xerces2-j/releases.html" target="_blank">http://xerces.apache.org/xerces2-j/releases.html</a> .<br>
Cheers<br>
<span class="HOEnZb"><font color="#888888">Alessio<br>
<br>
--<br>
Alessio Soldano<br>
Web Service Lead, JBoss<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</font></span></blockquote></div><br></div>