[ http://issues.apache.org/jira/browse/AXIS2-88?page=all ]
Deepal Jayasinghe resolved AXIS2-88:
------------------------------------
Fix Version: 0.9
Resolution: Fixed
It is already there and the way of registering custom messageReceiver as follows
<operation name="echoString">
<module ref="module1"/>
<messageReceiver
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
</operation>
We are sorry for lack of documentaion
> Support for registering custom MessageReceiver for an operation
> ---------------------------------------------------------------
>
> Key: AXIS2-88
> URL: http://issues.apache.org/jira/browse/AXIS2-88
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Components: deployment
> Versions: 0.9
> Reporter: Jayachandra Sekhara Rao Sunkara
> Fix For: 0.9
> Attachments: RegisterMessageReceiver.patch
>
> There can be cases where a few service implementation classes would demand
> special style of invocation (as is the case with me that my services if they
> are implementing ServiceLifeCycle interface I'd like to call special methods
> on them apart from the method that matches with the client requested
> operationName ). And in such cases if developers do code their custom
> MessageReceivers there should be a way to specify the same in the service or
> operation element of service.xml . And also our deployment should be embedded
> the intelligence to setMessageReceiver with that specified class rather than
> the default one.
> Thanks and Regards
> Jayachandra
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
