Hi Isuru, Thanks for the quick response! That really helped.
I was able to handle non-existing API contexts by referencing to mis-match handler sequence inside the main sequence; <sequence xmlns="http://ws.apache.org/ns/synapse"; name="main"> <in> <sequence key="_resource_mismatch_handler_"/> </in> </sequence> On Thu, Apr 23, 2015 at 11:31 PM, Isuru Udana <isu...@wso2.com> wrote: > Hi Akila, > > On Fri, Apr 24, 2015 at 11:55 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi, >> >> I'm trying to configure the _resource_mismatch_handler_ in ESB. I noticed >> that it gets triggered only when there is a mis-match for a resource in an >> already existing API context. It doesn't get triggered if a request is sent >> for a non-existing API context. >> >> Is this the expected behavior? >> > Yes. Synapse identify the api using the api context (not from API name). > So if the context is not matched, then it means there is no api to handle > that request and it is getting dispatched to the main sequence. > >> Is there any way to configure the mis-match handler for a non-existing >> API context? >> > No. From the name itself gives the idea of this sequence is for > mismatching resources. > However you many configure the main sequence logic to handle these type of > requests. > >> >> Thanks. >> >> -- >> Akila Ravihansa Perera >> Software Engineer, WSO2 >> >> Blog: http://ravihansa3000.blogspot.com >> > > > > -- > *Isuru Udana* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > -- Akila Ravihansa Perera Software Engineer, WSO2 Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
