[ https://issues.apache.org/jira/browse/AXIS2-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708827#action_12708827 ]
Charith Dhanushka Wickramarachchi commented on AXIS2-4347: ---------------------------------------------------------- the reason for giving a serviceUpdate notification when a module get engaged to a service or a operation is 1. its obviously a service update 2. as Andreas said if we need the information about which module engaged we need to change the API (add a method like moduleEngaged(...) ) to the AxisObserver , So i let the duty of finding which module engaged to the AxisObserver Implementation which can be easily done. > Improve Axis Observer Behaviour > ------------------------------- > > Key: AXIS2-4347 > URL: https://issues.apache.org/jira/browse/AXIS2-4347 > Project: Axis 2.0 (Axis2) > Issue Type: Wish > Environment: any > Reporter: Charith Dhanushka Wickramarachchi > Priority: Minor > Attachments: axis-observer.patch > > > Currently AxisObserver does not get notified when a Module engaged or > disengaged in the Runtime. > So to have that behaviour i would like purpose to add two Axis events Named > MODULE_ENGAGED , MODULE_DISENGAGED > and in the new behaviour when a module get engaged/disengaged to a Service > or to an Operation AxisObserver will get notified with > above Events. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.