[prev in list] [next in list] [prev in thread] [next in thread]
List: axis-dev
Subject: [jira] Resolved: (AXIS2-4347) Improve Axis Observer Behaviour
From: "Amila Chinthaka Suriarachchi (JIRA)" <jira () apache ! org>
Date: 2009-05-28 9:32:45
Message-ID: 1773686152.1243503165638.JavaMail.jira () brutus
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/AXIS2-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Amila Chinthaka Suriarachchi resolved AXIS2-4347.
-------------------------------------------------
Resolution: Fixed
applied the patch
> 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-28-05-2009.patch, axis-observer.patch, \
> 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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic