org.apache.catalina.startup.ContextConfig
processContextConfig
SEVERE: Occurred at line 2 column 28
- Original Message
From: Mark Thomas <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Saturday, January 27, 2007 2:16:25 PM
Subject: Re: XML Parse problem in a webapp context.xml
Pete wrote:
> Mark,
>
>
There is a partial stack trace in the original message ( cut the middle out),
but I can get the complete one for you on Monday.
-P
- Original Message
From: Mark Thomas <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Saturday, January 27, 2007 2:16:25 PM
Subject: Re: XML Parse problem
n get the complete one for you on Monday.
-P
- Original Message
From: Mark Thomas <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Saturday, January 27, 2007 2:16:25 PM
Subject: Re: XML Parse problem in a webapp context.xml
Pete wrote:
> Mark,
>
> I stated in the origi
Pete wrote:
> Mark,
>
> I stated in the original message that the conf/web.xml is unmodified and the
> problem only happens with certain contents in the META-INF/context.xml after
> it gets moved from the app into conf/Catalina/localhost directory.
>
> -P
Sorry - my bad. I should have read you
TED]>
To: Tomcat Users List
Sent: Friday, January 26, 2007 7:25:19 PM
Subject: Re: XML Parse problem in a webapp context.xml
Pete wrote:
> SEVERE: Parse error in default web.xml
This may be the real cause. Check that conf/web.xml is va
Pete wrote:
> SEVERE: Parse error in default web.xml
This may be the real cause. Check that conf/web.xml is valid
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additio
/jndi-datasource-examples-howto.html#Non%20DBCP%20Solutions)
From the HOWTO:
?-P
- Original Message
From: Robert Harper <[EMAIL PROTECTED]>
To: Tomcat Users List
Sent: Friday, January 26, 2007 1:22:19 PM
Subject: RE: XML Parse problem in a webapp context.xml
There are pr
riginal Message-
From: Pete [mailto:[EMAIL PROTECTED]
Sent: Friday, January 26, 2007 12:05 PM
To: users@tomcat.apache.org
Subject: XML Parse problem in a webapp context.xml
Hello all,
I've searched high and low before posting tried every test I could think of
before posting here... Th
Hello all,
I've searched high and low before posting tried every test I could think of
before posting here... This problem seems too simple to be a bug, but can't
find a method of resolving it.
I decided to skip the port of our application (ran fine on WAS 6 - JVM 1.5)
that was that originated
