You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Rui Alberto L. Gonçalves" <ru...@ptinovacao.pt> on 2003/11/13 18:27:42 UTC
internal pipeline error handling!
Hi all,
in my sitemap I have:
<map:selectors default="request">
<map:selector logger="sitemap.selector.exception" name="exception"
src="org.apache.cocoon.selection.ExceptionSelector">
<exception class="java.net.ConnectException"
name="connection-refused"/>
...
</map:selector>
</map:selctors>
<map:pipelines>
<map:pipeline internal-only="true">
<!--MYGENERATOR may throw java.net.ConnectException-->
<map:match pattern="xpto">
<map:generate type="MYGENERATOR">
<map:serialize type="xml"/>
</map:match>
<map:handle-errors>
<map:select type="exception">
<map:when test="connection-refused">
<map:read src="html/errors/connection-refused.html"
mime-type="text/html"/>
</map:when>
...
</map:handle-errors>
</map:pipeline>
<map:pipeline>
somewhere calls cocoon://xpto
</map:pipeline>
.....
If MYGENERATOR throws an java.net.ConnectException
this exception is not catched in handle-errors inside
internal pipeline?
Don't know why but I always get the default cocoon error page!
Could someone give me a hint please?!!
Thanks in advance!!
Rui Alberto
--
Rui Alberto L. Gonçalves <ru...@ptinovacao.pt>
PT Inovação
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org