axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grégory Provost (JIRA) <>
Subject [jira] Created: (AXIS2-3962) Engagle custom handlers per operation
Date Mon, 04 Aug 2008 07:31:44 GMT
Engagle custom handlers per operation

                 Key: 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


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="">
	            <actionMapping>ping</actionMapping>	            <outputActionMapping></outputActionMapping>
	            <faultActionMapping faultName="NotaryFault">urn:PingNotaryFault</faultActionMapping>
	            <faultActionMapping faultName="FaultName"></faultActionMapping>

<operation name="QueryOnNationalNumber" mep="">
   <module ref="enotaryModule"/> 
	            <faultActionMapping faultName="NotaryFault">urn:QueryOnNationalNumberNotaryFault</faultActionMapping>
	            <faultActionMapping faultName="FaultName"></faultActionMapping>

Problem: the module is still engaged at service level !!!!!! and not only for the "QueryOnNationalNumber"

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?



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:
For additional commands, e-mail:

View raw message