[ http://issues.apache.org/jira/browse/AXIS2-657?page=all ]
Deepal Jayasinghe resolved AXIS2-657:
-------------------------------------
Resolution: Fixed
fixed in current SVN
> Module engagement does not work for single services or service groups when
> using the web frontend
> -------------------------------------------------------------------------------------------------
>
> Key: AXIS2-657
> URL: http://issues.apache.org/jira/browse/AXIS2-657
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Versions: 1.0
> Environment: Axis2 1.0 RC4
> Reporter: Thilo Frotscher
>
> I created a module archive (mar) that contains 1 handler class and configured
> module.xml so that this handler belongs to a user-defined phase of the IN
> flow.
> After that I added this user-defined phase to the IN flow by editing axis2.xml
> 1) Engaging the module globally to all services works fine.
> 2) Engaging the module to specific operations works fine, too.
> 3) Engaging the module to a single service or service group does not work,
> and there is not message displayed whether the engagement was succesful or
> unsuccesful like in cases 1) and 2)
> By the way: when engaging the module to all services, my modules method
> engageNotify is invoked 13 times, even though there are only 3 services with
> a total of 5 operations.
--
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
