Thanks for your help. The problem was that, but not in Tomcat. I am running an application that uses CAS to log, and the exception was thrown in that application, so I had to place the jars in the endorsed folder of the app server.
Marvin Addison-2 wrote: > >> I´ve been looking for a solution, but all the information I have found >> sais >> that the problems must be relationed with an old version of xerces >> library. >> I´m using Xerces 2.9.1, so I think that´s not the problem. > > One likely problem is that you have not endorsed the Xerces parser as > the default XML parsing library used by Tomcat. Try placing the > following jars in the directory $TOMCAT_HOME/common/endorsed and see > if that helps: > > xalan-$VERSION.jar > xalan-$VERSION-serializer.jar > xerces-$VERSION-xercesImpl.jar > xerces-$VERSION-xml-apis.jar > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- View this message in context: http://www.nabble.com/CAS-SAML-setFeature-tp23614009p23665442.html Sent from the CAS Users mailing list archive at Nabble.com. -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
