On Wed, May 6, 2009 at 12:52 AM, Makesh Rao <[email protected]> wrote:
> Hi > We are planning to build a custom module in Axis2 that is required to get > enabled in INOnly, INOUT & OutOnly patterns. > We have a webservice that will use this implementation. I had some doubts > on how Axis2 behaves in the OutOnly mode (or even OutIn). > At the server side axis2 handles the MEP (message exchange pattern at the Message receiver level). So you handler can be used in both cases without any problem. > > The use case is that our service calls another client webservice and the > request has to go through our cus > tom module --> OutIn or OutOnly > Similarly when any other service calls our service the request should go > through the custom module again. -> InOut. > > 1. For OutOnly or OutIn, do we have to use the generated client > implementation and engage the custom module in that ? > yes. > 2. How will the response to that request be handled ? Will it come in > through the "server" axis listener ? > This depends on the way you do the invocation. If you use a synchronous (default mode) invocation response comes in the back channel. This is almost same as you invoke it as a separate client. this article[1] may help you. thanks, Amila. [1] http://wso2.org/library/articles/extending-axis2 > > Any help is appreciated.. > > Thanks > Makesh > > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
