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
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?
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
~
Context
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
OK, my conf files were like that:
~
!--
Context configuration file for the Tomcat Manager Web App
$Id: manager.xml 287893 2002-04-08 17:46:08Z craigmcc $
Context
Linux Box:
path=/manager
docBase=/media/sda2/inst/sw/java/TC/tc4.1/apache-tomcat-4.1.36/server/webapps/manager
Windows
What I see below is a comment !-- -- block that does not
encompass both the beginning and ending Context 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
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 Context elements. This
would
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
