At 10:46 am +0300 26/3/02, Piroumian, Konstantin wrote:
>> 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).
Thanks for the confirmation.
>>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.
I think we have a problem :(
I occasionally notice a completely new error page, in pink Courier, is this
part of what Nicola Ken is doing to the error reporting mechanism?
regards Jeremy
--
___________________________________________________________________
Jeremy Quinn Karma Divers
webSpace Design
HyperMedia Research Centre
<mailto:[EMAIL PROTECTED]> <http://www.media.demon.co.uk>
<phone:+44.[0].20.7737.6831> <pager:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
