|
Hi All, According the current
implementation of Axis2, when we deploy a service, we can specify one
MessageReceiver (InOnlyMessageReceiver, InOutMessageReceiver etc..) per
service. According to my understanding we should let the user to register one
MessageReceiver per operation basis. Possible example would be as follows. We have a web service with
IN-ONLY operation. However we need to let the service to implement the RequestSecurityToken operation according to the WS-SecCon. This operation is an IN-OUT operation. In this
situation we have to register two message receivers to these two operations. In
addition, the MEP is bind to an operation and the MessageReceiver is the one
who is driving the MEP. So I think we have let each operation to have its own
message receiver. thoughts ?? Thanks, Jaliya |
- [Axis2] Deploying MessageReceivers per Operation Jaliya Ekanayake
- Re: [Axis2] Deploying MessageReceivers per Operatio... Deepal Jayasinghe
- RE: [Axis2] Deploying MessageReceivers per Oper... Chathura Herath
- RE: [Axis2] Deploying MessageReceivers per ... Jaliya Ekanayake
- RE: [Axis2] Deploying MessageReceivers ... Chathura Herath
- Re: [Axis2] Deploying MessageRecei... Jaliya Ekanayake
- Re: [Axis2] Deploying MessageR... Srinath Perera
- RE: [Axis2] Deploying Mess... Chathura Herath
- Re: [Axis2] Deploying Mess... Deepal Jayasinghe
