if you find exceptions looking like this:
~
org.apache.commons.digester.Digester endElement
SEVERE: End event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:217)
at org.apache.commons.digester.Rule.end(Rule.java:253)
at org.apache.commons.digester.Digester.endElement(Digester.java:1222)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
. . .
~
it means what is says ;-)
~
but what I think is wrong is that TC conf parsers apparently attempt
to parse into the comments so that if you have some not well-formed
xml inside the comments, such as:
~
<!--
Context configuration file for the Tomcat Administration Web App
$Id: admin.xml 288428 2002-07-23 12:12:15Z remm $
W Box at Work:
<Context
docBase="C:\cmllpz\prjx\java\GWB\tc\tc-4.1.36\server\webapps\admin"
<Logger
directory="C:\cmllpz\prjx\java\GWB\logs"
-->
~
they would pick it up
~
I was using TC 4.1.36 but I think this is a bug. After being fed a
start comment, "<!--", sequence parsers should not attempt to resume
parsing till they fully get an ending, "-->", one
~
Or?
~
lbrtchx
---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
