axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Afkham Azeez (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-3962) Engagle custom handlers per operation
Date Thu, 06 Jan 2011 08:47:46 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Afkham Azeez resolved AXIS2-3962.
---------------------------------

    Resolution: Not A Problem

> Engagle custom handlers per operation
> -------------------------------------
>
>                 Key: AXIS2-3962
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3962
>             Project: 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.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message