Hello,

I have a template where I *Call* a *Address* mediator. However, during the
runtime, I have a network problem which causes it to explode with a
graceful java.net.NoRouteToHostException. Of course, I will have to fix the
network part but, in the same time, I would like to be able to continue my
process.

My template is something like:

<template name="getCommonConfigurationParameter" xmlns="
> http://ws.apache.org/ns/synapse";>
>     <parameter name="targetParamName"/>
>     <parameter name="paramToSetName"/>
>     <sequence onError="commonServiceFaultSequence"
> name="getCommonConfigurationParameterSequence">
>         <property description="uri.var.parameterRetrievalEndpoint"
> expression="fn:concat($ctx:commonConfigurationUrl, '/parameters/name/',
> $ctx:targetParamName)" name="uri.var.parameterRetrievalEndpoint"
> scope="default" type="STRING"/>
>         <property action="remove" description="remove REST_URL_POSTFIX"
> name="REST_URL_POSTFIX" scope="axis2"/>
>         <property action="remove" description="remove Accept"
> name="Accept" scope="transport"/>
>         <property name="HTTP_METHOD" scope="axis2" type="STRING"
> value="GET"/>
>         <call blocking="true">
>             <endpoint>
>                 <address uri="${uri.var.parameterRetrievalEndpoint}">
>                     <timeout>
>                         <duration>2</duration>
>                         <responseAction>fault</responseAction>
>                     </timeout>
>                 </address>
>             </endpoint>
>         </call>
>
</template>
>

And my "recovery" sequence, named commonServiceFaultSequence , is like that:

<?xml version="1.0" encoding="UTF-8"?>
> <sequence name="commonServiceFaultSequence" trace="disable" xmlns="
> http://ws.apache.org/ns/synapse";>
>     <log level="custom">
>         <property name="message" value="TEST"/>
>     </log>
> </sequence>
>

Have you got any idea?

Regards,

Thomas
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to