On 10.06.2004 16:16, Simon Hutchinson wrote:
Hi,
I have written a pipeline with the following error handler
<map:handle-errors>
<map:select type="exception"> <map:when test="processing">
<map:generate src="root.xml"/>
<map:transform src="xsl/error.xsl">
<map:parameter name="err" value="processing"/>
</map:transform>
<map:transform type="i18n"/>
<map:serialize/>
</map:when>
<map:otherwise>
<map:generate src="root.xml"/>
<map:transform src="xsl/error.xsl">
<map:parameter name="err" value="other"/> </map:transform>
<map:transform type="i18n"/>
<map:serialize/>
</map:otherwise> </map:select>
</map:handle-errors>
ie If an exception thrown and it is a processing exception then the output will read "processing" otherwise the output will read "other"
When I navigate to this pipeline (designed to throw an exception) then the handle-errors section is invoked and my error message is returned.
However I have a coplet whose URI is this same pipeline, when the coplet call the pipeline the error is thrown but the handle-errors section is never entered and my error message is never thrown,
Could anyone shed any light on why the error handler is not entered when
the pipeline is called by a coplet and if possible how to correctly handle exceptions within the portal framework
Coplet is an internal pipeline, isn't it? There are discussions how to handle errors for internal pipelines correctly on the dev list. At the moment it is not possible.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
