Past weekend I just went thru xerces *e&l% on another Application Server ..turns out they had a DTD specific xerces version that gacked on xsds The AppServer version of Xerces was buried so far down into the core their solution was to rebuild the server with a version of Xerces that wont fubar on parsing xsds NB: 99% of the posts I've seen for xerces problems say "delete all versions of xerces from your CLASSPATH"
Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > From: chuck.caldar...@unisys.com > To: users@tomcat.apache.org > Date: Mon, 12 Dec 2011 21:57:55 -0600 > Subject: RE: Tomcat xerces conflicts and Endorsed,Standards Override Mechanism > > > From: Mark Eggers [mailto:its_toas...@yahoo.com] > > Subject: Re: Tomcat xerces conflicts and Endorsed,Standards Override > > Mechanism > > > > servlet-api-2.3.jar > > > servlet-api-2.5.jar > > > If you're using Maven to manage the dependencies, how about > > marking the offending jars <scope>provided</scope>, and see > > if the later versions provided in the JRE (and in Tomcat for > > the servlet spec) meet the expected requirements. > > At the very least, the OP _must_ remove the servlet-api*.jar files; they are > provided by the container and can never be placed in WEB-INF/lib. (But > they're not the cause of the XML problem, just another symptom.) > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
