> From: Jeremy Quinn [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 25, 2002 11:20 PM > To: Cocoon Dev > Subject: error response broken? > > > 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 <slash-edit/>. > > 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 "</title>". > > 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.
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). >You can replicate it by running <slash-edit/> 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. Konstantin > >regards Jeremy > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
