David Smith wrote:
Thanks.
It's an interesting problem. It does validate against an xml validator,
but I can't reproduce your error in my tomcat 5.5 environment. If it's
really an error w/ tomcat, it has to be unique to your version of
tomcat. Any one on this list still using tomcat 4.1 wan
Thanks.
It's an interesting problem. It does validate against an xml validator,
but I can't reproduce your error in my tomcat 5.5 environment. If it's
really an error w/ tomcat, it has to be unique to your version of
tomcat. Any one on this list still using tomcat 4.1 want to respond?
--D
OK, my conf files were like that:
~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~
and what I believe to be a bug is that conf parsers should not pick
anything between ""
~
lbrtchx
-
To start a ne
Sorry but you're still posting only a partial context.xml file and it
still looks like invalid XML. Get a XML validator and check your
files. I know NetBeans has one built-in. To illustrate the whole valid
vs. invalid point:
Valid xml -- note the invalid xml fragment wrapped in a comment so
David,
~
sorry for my delay . . .
~
there is nothing to be shown. it is a config issue which you could
reproduce by:
~
1) downloading tc 4.1.36
~
2) giving it a first run to make sure everything is OK
~
2) writing, within the admin.xml or manage.xml conf files, something like
~
wrote:
> I ju
I just realized what you posted was just a very narrow excerpt of the
comment block only. Could you provide a complete example?
--David
David Smith wrote:
What I see below is a comment block that does not
encompass both the beginning and ending elements. This
would fail if run through a X
What I see below is a comment block that does not
encompass both the beginning and ending elements. This would
fail if run through a XML validator. If the begin element is in the
comment, so should it's corresponding end element. Additionally be
careful you don't try to nest comments. --
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(NativeMethodA
