Grzegorz Kossakowski-3 wrote:
>
>
> Could you repeat rephrased description of your problem again? What do you
> want to achieve, what are obstacles?
>
Sure,
i think it is a general problem in cocoon 2.2 to handle a request in
sitemap, that belong to / (root) request.
e.g.
127.0.0.1/
127.0.0.1/favicon.ico
127.0.0.1/whatever.html
The problem for me seems to be that all in "/" is treated as block, not as
"pipeline-possible" (even the case if you set the mountpath to / in the
definition). So you will receive a "no block for ..." message and not a "no
pipeline matched". So i guess cocoon tries to get a "whatever.html" block
instead of sending the request to its block mounted with /.
If you change to:
127.0.0.1/myBlock1/
127.0.0.1/myBlock1/favicon.ico
127.0.0.1/myBlock1/whatever.html
Then it is no problem, since all request are triggered to the sitemap.xmap
of myBlock1 block.
Alex
--
View this message in context:
http://www.nabble.com/-cocoon-2.2.x----javax.servlet.ServletException%3A-No-block-for--favicon.ico-tf4083579.html#a11648540
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
