[
https://issues.apache.org/jira/browse/AXIS2-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4347:
-----------------------------------
Priority: Minor (was: Major)
Issue Type: Wish (was: Bug)
To me, the solution doesn't look generic enough because the observer doesn't
get any information about which module has been engaged. Also, if the target is
an operation, the observer only gets a reference to the service.
What is actually the use case for this?
> 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.
