I thought that was the problem, but thought I had removed all references
to the Xerces that my app uses.
It turns out I had all my tomcat projects adding themselves to the tomct
classpath.
I know i had a good reason at the time, but that was the cause of the
problem
Thanks
Steve
Varley, Roger wrote:
Well, check you Sysdeo Plugin settingts. See if they point to a
different server.xml file. From the stack trace it appears the
server.xml is broken. Usually this file is found in
<tomcat>/conf/server.xml but Sysdeo plugin might have changed it.
Could this be caused by Tomcat using a different version of Xerces when it
starts under Eclipse. I know I've read of problems when Tomcat gets hold of the
wrong version of Xerces (and Xalan as well) in the past, but I can't remember
where I've read it. Perhaps someone elses memory may be jogged.
Regards
Roger
_______________________________________________________
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive this
e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the
sender does not warrant that this transmission is virus-free and will
not be liable for any damages resulting from any virus transmitted.
_______________________________________________________
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
