The response comes back through the same valve; within a valve's invoke method, you normally call the invoke method of the next valve as follows: getNext().invoke(request, response);
That is how valve chaining works. So, soon after the getNext().invoke(request, response); line, you can get hold of the response, and extract whatever you may need. On Tue, Jun 25, 2013 at 7:53 PM, Nuwan Dias <[email protected]> wrote: > Hi, > > As a part of getting API Management into the platform, we have used a > tomcat valve to intercept incoming service requests and perform API > Management functionalities. We are currently doing this for the GREG's REST > API. > > The problem we're facing now is that although the request can be > intercepted using the valve, the response does not go back through it. The > need of this requirement is to intercept responses and publish response > stats to BAM. > > Is there a way to intercept responses through the valve, or is there any > alternative ways of getting this done? > > Thanks, > NuwanD. > > -- > Nuwan Dias > > Senior Software Engineer - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
