You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Charith Dhanushka Wickramarachchi (JIRA)" <ji...@apache.org> on 2009/05/13 08:36:45 UTC

[jira] Created: (AXIS2-4347) Improve Axis Observer Behaviour

Improve Axis Observer Behaviour
-------------------------------

                 Key: AXIS2-4347
                 URL: https://issues.apache.org/jira/browse/AXIS2-4347
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
         Environment: any
            Reporter: Charith Dhanushka Wickramarachchi


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.


[jira] Updated: (AXIS2-4347) Improve Axis Observer Behaviour

Posted by "Charith Dhanushka Wickramarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charith Dhanushka Wickramarachchi updated AXIS2-4347:
-----------------------------------------------------

    Attachment: axis-observer.patch

> Improve Axis Observer Behaviour
> -------------------------------
>
>                 Key: AXIS2-4347
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4347
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>         Environment: any
>            Reporter: Charith Dhanushka Wickramarachchi
>         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.


[jira] Updated: (AXIS2-4347) Improve Axis Observer Behaviour

Posted by "Charith Dhanushka Wickramarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charith Dhanushka Wickramarachchi updated AXIS2-4347:
-----------------------------------------------------

    Attachment: axis-observer.patch

This is done according to the way purposed by Deepal by adding a AxisDescription reference to the AxisEvent
 

> 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, 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.


[jira] Commented: (AXIS2-4347) Improve Axis Observer Behaviour

Posted by "Charith Dhanushka Wickramarachchi (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Updated: (AXIS2-4347) Improve Axis Observer Behaviour

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Updated: (AXIS2-4347) Improve Axis Observer Behaviour

Posted by "Charith Dhanushka Wickramarachchi (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charith Dhanushka Wickramarachchi updated AXIS2-4347:
-----------------------------------------------------

    Attachment: axis-observer-28-05-2009.patch

just updated the patch to current revision 

> 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.


[jira] Resolved: (AXIS2-4347) Improve Axis Observer Behaviour

Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
     [ 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.