On Sun, 26 Aug 2001, cib wrote:
> Date: Sun, 26 Aug 2001 23:17:29 +0200
> From: cib <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED], cib <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Start up Sax exception init param
>
> Thanks for answering
> But, do you mean the error is from the cocoon "web.xml" file or the tomcat
> one?
Since you didn't give us the entire error traceback, it's impossible to
tell -- but if it were the Tomcat one, it would cause problems for *all*
web apps, not just this one.
> As I have only changed the cocoon jar, i guess it's from the cocoon one.
> Here is line 181
>
>
> <!--
> This parameter allows you to startup Cocoon2 immediately after startup
> of your servlet engine.
> -->
> <load-on-startup>1</load-on-startup>
> </servlet>
>
Please cut-and-paste the *entire* <servlet> element -- if things are out
of order, we can't tell from just this.
Craig
> Nobody answered my question on the cocoon user mailing list, maybe it was
> badly fomulated.
>
> ----- Original Message -----
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> To: "Tomcat User Mail List" <[EMAIL PROTECTED]>; "cib"
> <[EMAIL PROTECTED]>
> Sent: Thursday, August 23, 2001 5:48 PM
> Subject: Re: Start up Sax exception init param
>
>
> >
> >
> > On Thu, 23 Aug 2001, cib wrote:
> >
> > > Date: Thu, 23 Aug 2001 08:54:24 +0200
> > > From: cib <[EMAIL PROTECTED]>
> > > Reply-To: [EMAIL PROTECTED], cib <[EMAIL PROTECTED]>
> > > To: Tomcat User Mail List <[EMAIL PROTECTED]>
> > > Subject: Start up Sax exception init param
> > >
> > > Hi,
> > > I've upgraded to Cocoon2.0b1 from beta1.
> > > But since I changed the war old war file to the new one ( I've erased
> the
> > > "work" directory before, idem for the log files), I get an exception at
> > > Tomcat's start. No one answered my question on cocoon mailing list, so I
> try
> > > it here.
> > > The exception is:
> > >
> > > PARSE error at line 181 column -1
> > > org.xml.sax.SAXParseException: org.apache.crimson.parser/V-036 web-app
> > > init-param
> > >
> >
> > This sounds like there might be a problem with your web.xml file at line
> > 181. In particular, if you have the elements in an order different than
> > what the DTD requires, you will *always* get XML validation errors.
> >
> > Craig McClanahan
> >
>
>
