[jira] Commented: (AXIS2-3962) Engagle custom handlers per operation

["Sharath Reddy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AXIS2-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671160#action_12671160 ] 

Sharath Reddy commented on AXIS2-3962:
--------------------------------------


It works fine for me with Axis2 1.4.1 - I was able to engage module at operation level. 

One thing to keep in mind is that Operation-level modules should be defined AFTER the Dispatch phase. 

My axis2.xml file had the phase <phase name="OperationInPhase"> defined after the Dispatch phase, so I used this phase in my module.xml file:

<order phase="OperationInPhase" />

The rest of my settings are exactly as yours. 

> Engagle custom handlers per operation
> -------------------------------------
>
>                 Key: AXIS2-3962
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3962
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: modules
>    Affects Versions: 1.3
>         Environment: Windows XP SP2 - Axis 1.3 - Rampart 1.3
>            Reporter: Grégory Provost
>            Priority: Minor
>
> Hello,
> I'm using Axis 1.3.
> I'm using a module (<order phase="Dispatch" />)  with several custom handlers.  Everything is working fine when the module is engaged at service level (service.xml : <module ref="enotaryModule"/>).
> I'm now trying to engage the same module but at operation level (Reason : no validation required for the Ping operation).
> In order to perfom that, I modified my service.xml in order to register my module for one particular operation:
> 	        <operation name="Ping" mep="http://www.w3.org/ns/wsdl/in-out">
> 	            <actionMapping>ping</actionMapping>	            <outputActionMapping>http://wsdl.notary.be/QueryPhysicalPersonService/QueryPhysicalPersonService/PingResponse</outputActionMapping>
> 	            <faultActionMapping faultName="NotaryFault">urn:PingNotaryFault</faultActionMapping>
> 	            <faultActionMapping faultName="FaultName">http://wsdl.notary.be/QueryPhysicalPersonService/QueryPhysicalPersonService/Ping/Fault/FaultName</faultActionMapping>
> 	        </operation>
> <operation name="QueryOnNationalNumber" mep="http://www.w3.org/ns/wsdl/in-out">
>    <module ref="enotaryModule"/> 
>    <actionMapping>QueryOnNationalNumber</actionMapping>
> <outputActionMapping>http://wsdl.notary.be/QueryPhysicalPersonService/QueryPhysicalPersonService/QueryOnNationalNumberResponse</outputActionMapping>
> 	            <faultActionMapping faultName="NotaryFault">urn:QueryOnNationalNumberNotaryFault</faultActionMapping>
> 	            <faultActionMapping faultName="FaultName">http://wsdl.notary.be/QueryPhysicalPersonService/QueryPhysicalPersonService/QueryOnNationalNumber/Fault/FaultName</faultActionMapping>
> </operation>
> Problem: the module is still engaged at service level !!!!!! and not only for the "QueryOnNationalNumber" operation.
> I also tried to engage the module dynamically using the ServiceLifeCycle (startUp event).  But at this stage the AxisService is not yet fully configured and does not contain any AxisOperation (service.getOperations empty).
> Do I miss something something with the configuration?
> Thanks
> Grégory

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.