Return-Path: 
 <cocoon-dev-return-24861-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 50839 invoked by uid 500); 26 Mar 2002 15:00:25 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 50826 invoked from network); 26 Mar 2002 15:00:25 -0000
Mime-Version: 1.0
X-Sender: media@pop3.demon.co.uk
Message-Id: <a05101419b8c6293c73f7@[10.0.1.40]>
In-Reply-To: <00c601c1d4c8$7ac604f0$670004c0@PC103>
References: <092C4B8A9B51D411829E00D0B749AFBBA831FE@post.flagship.ru>
 <002d01c1d4b3$7864c8f0$670004c0@PC103>
 <a05101411b8c613bd6a55@[10.0.1.40]> <00c601c1d4c8$7ac604f0$670004c0@PC103>
Date: Tue, 26 Mar 2002 15:01:02 +0000
To: cocoon-dev@xml.apache.org
From: Jeremy Quinn <jeremy@media.demon.co.uk>
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 2:16 pm +0100 26/3/02, Nicola Ken Barozzi wrote:
>From: "Jeremy Quinn" <jeremy@media.demon.co.uk>
>
>> At 11:46 am +0100 26/3/02, Nicola Ken Barozzi wrote:
>> >From: "Piroumian, Konstantin" <KPiroumian@flagship.ru>
>> >
>> >> > 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 <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.
>> >
>> >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.
>
>It's not so wierd.
>
>With the current Cocoon version of the editor, it says that it can't fint
>"test.xmap".
>In fact, test.xmap is mounted just after editor.xmap in your sitemap.
>
><!-- start EDITING PIPELINES -->
><!-- We mount the Editor SiteMap into the same base as this
>       SiteMap, so the Editor can reach this SiteMap's files -->
>
>   <!-- slash-edit pipeline -->
>   <!-- edit/, edit/new/*, edit/get/*, edit/put, edit/view/* -->
>   <map:match pattern="edit**">
>    <map:mount uri-prefix="edit" src="editor.xmap" check-reload="yes"/>
>   </map:match>
>
>   <!-- test/result pipeline -->
>   <!-- /test/*, /result/*, result/*/* -->
>   <map:match pattern="*/**">
>    <map:mount uri-prefix="" src="test.xmap" check-reload="yes"/>
>   </map:match>
>
><!-- end EDITING PIPELINES -->
>
>This means that the matcher doesn't match where you would want it to but
>matches the test.xmap pipeline part.
>There is has problems in finding the file.
>
>If I remove the test.xmap mount, it behaves like you say.
>In fact, it tries to use the parent sitemap to match, matches somewhere, but
>can't find the file it's looking for (simple-page2html.xsl) because resolves
>the parent sitemap definitions relative to *his* context, which has always
>happened.
>
>Now the question is:
>Why doesn't it match where you want it to match?
>
>See, the error is not directly about the wrong xml AFAIS, but something
>else.
>Side effect components tend to have this problem with the errors, because
>side effects are no directly specified in the pipeline.
>
>Can this help you a bit?

Thanks for looking into this.

I noticed the issue about test.xmap and changed the sitemap.xmap
accordingly (but did not commit) :

			<map:match pattern="test/**">
				<map:mount uri-prefix="" src="test.xmap" check-reload="yes"/>
			</map:match>

			<map:match pattern="result/**">
				<map:mount uri-prefix="" src="test.xmap" check-reload="yes"/>
			</map:match>

It is still getting lost though.

The big issue as I see it is that before last week, the exact same sitemap
(as the one now in CVS) produced different results.

regards Jeremy
-- 
   ___________________________________________________________________

   Jeremy Quinn                                           Karma Divers
                                                       webSpace Design
                                            HyperMedia Research Centre

   <mailto:sharkbait@mac.com>     		 <http://www.media.demon.co.uk>
   <phone:+44.[0].20.7737.6831>             <pager:jermq@vizzavi.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org