Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 3021 invoked by uid 500); 26 Mar 2002 12:05:51 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 3010 invoked from network); 26 Mar 2002 12:05:50 -0000 Mime-Version: 1.0 X-Sender: media@pop3.demon.co.uk Message-Id: In-Reply-To: <002d01c1d4b3$7864c8f0$670004c0@PC103> References: <092C4B8A9B51D411829E00D0B749AFBBA831FE@post.flagship.ru> <002d01c1d4b3$7864c8f0$670004c0@PC103> Date: Tue, 26 Mar 2002 12:06:11 +0000 To: cocoon-dev@xml.apache.org From: Jeremy Quinn Subject: Re: error response broken? Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N At 11:46 am +0100 26/3/02, Nicola Ken Barozzi wrote: >From: "Piroumian, Konstantin" > >> > From: Jeremy Quinn [mailto:jermq@media.demon.co.uk] >> > >> > Dear All, >> > >> > I have noticed a big change in the way Cocoon responds to >> > errors caused by >> > you putting mal-formed xml into a field in . >> > >> > Up until a week ago (I got a bit behind CVS) Cocoon would >> > respond with a >> > normal message like: >> > >> > Original exception : org.xml.sax.SAXParseException: The element type >> > "title" must be terminated by the matching end-tag "". >> > >> > etc. >> > >> > Now it says things like: >> > >> > Original exception : java.io.FileNotFoundException: >> > /Users/jermq/Library/TomCat/webapps/cocoon/stylesheets/simple- >> > page2html.xsl >> > (No such file or directory) >> > >> > Which is strange. > >Try commenting out the transformation in the handle-errors and serializing >to xml, you will always see the error. I tried this ...... commented out the transformation and HTML serialization in the error-handlers in mount/editor/sitemap.xmap and mount/editor/editor.xmap, replacing them with a straight serialize to XML. I still get the weird error, where it trounces off looking for nonsense. >> I'm getting something similar for JSP sample pages. And also couldn't get >> correct error message for the i18n samples (it was also >> FileNotFoundException while the files was there for sure). > >Cocoon has problems on some errors, and > >> >You can replicate it by running and making a new file in >the >> >Alpha Editor, then make the new XML invalid and submit. >> > >> >Any ideas what might have got changed to cause this? >> >It seems like the sitemap is getting lost ;) >> >> And this happened during last week. Last week version from CVS worked just >> fine. > >I'll look into it, but right now I haven't got a clue :-/ Thanks! Both Konstantin and I think it happened early last week, so that is the only clue I have to offer, sorry. regards Jeremy -- ___________________________________________________________________ Jeremy Quinn Karma Divers webSpace Design HyperMedia Research Centre --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org