axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe" <dee...@opensource.lk>
Subject Re: [jira] Commented: (AXIS2-88) Support for registering custom MessageReceiver for an operation
Date Thu, 21 Jul 2005 07:50:59 GMT
Hi jaya

It is already there no need to re-implement it , as you have said if a 
operation tag dose not contains a MessageRecievr then the default one 
RowXMLInoutMessageReceiver will be the message receiver for the operation.

We encounter this kind of problem since we are lack of documentation.


Thanks,
 Deepal
................................................................
~Future is Open~



----- Original Message ----- 
From: "Jayachandra Sekhara Rao Sunkara (JIRA)" <jira@apache.org>
To: <axis-dev@ws.apache.org>
Sent: Thursday, July 21, 2005 1:06 PM
Subject: [jira] Commented: (AXIS2-88) Support for registering custom 
MessageReceiver for an operation


>    [ 
> http://issues.apache.org/jira/browse/AXIS2-88?page=comments#action_12316320 ]
>
> Jayachandra Sekhara Rao Sunkara commented on AXIS2-88:
> ------------------------------------------------------
>
> Deepal!
> If the above description looks valid, have a look at my tiny patch that 
> does the job. If that looks agreeable in your review, can you patch it up 
> in the org/.../deployment/DeploymentParser.java file.
>
> Broadly, the patch aims to support
>
> <operation name="coreOperation" 
> messageReceiver="com.myorg.newLifecycleReceiver">
> </operation>
>
> kind of construct in service.xml, provided the class given against 
> messageReceiver is loadable and instantiable.
>
> The attached patch is svn creted patch from the 
> org/apache/axis2/deployment folder. The patch is tested, build is 
> successful.
>
> Thank you
> Jayachandra
>
>> 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
>>  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
>
>
> 



Mime
View raw message