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 "nadir amra (JIRA)" <ji...@apache.org> on 2007/04/20 04:50:15 UTC

[jira] Created: (AXIS2-2567) Exploded POJO service always activated even if deactivated from ADMIN console

Exploded POJO service always activated even if deactivated from ADMIN console
-----------------------------------------------------------------------------

                 Key: AXIS2-2567
                 URL: https://issues.apache.org/jira/browse/AXIS2-2567
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: deployment
    Affects Versions: nightly
            Reporter: nadir amra


Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-2567) Service activation with hotupdate not correct

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507436 ] 

Davanum Srinivas commented on AXIS2-2567:
-----------------------------------------

Deepal,

this is fixed now. right?

thanks,
dims

> Service activation with hotupdate not correct
> ---------------------------------------------
>
>                 Key: AXIS2-2567
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2567
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: nightly
>            Reporter: nadir amra
>            Assignee: Deepal Jayasinghe
>
> Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.
> For aar files, this seems to work fine.  However, if the aar file is updated, the state goes to active.  I would think in this case it should still be inactive.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Resolved: (AXIS2-2567) Service activation with hotupdate not correct

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

Davanum Srinivas resolved AXIS2-2567.
-------------------------------------

    Resolution: Fixed

> Service activation with hotupdate not correct
> ---------------------------------------------
>
>                 Key: AXIS2-2567
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2567
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: nightly
>            Reporter: nadir amra
>            Assignee: Deepal Jayasinghe
>
> Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.
> For aar files, this seems to work fine.  However, if the aar file is updated, the state goes to active.  I would think in this case it should still be inactive.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Updated: (AXIS2-2567) Service activation with hotupdate not correct

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

nadir amra updated AXIS2-2567:
------------------------------

    Summary: Service activation with hotupdate not correct  (was: Exploded POJO service always activated even if deactivated from ADMIN console)

> Service activation with hotupdate not correct
> ---------------------------------------------
>
>                 Key: AXIS2-2567
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2567
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: nightly
>            Reporter: nadir amra
>
> Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.
> For aar files, this seems to work fine.  However, if the aar file is updated, the state goes to active.  I would think in this case it should still be inactive.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Updated: (AXIS2-2567) Exploded POJO service always activated even if deactivated from ADMIN console

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

nadir amra updated AXIS2-2567:
------------------------------

    Description: 
Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.

For aar files, this seems to work fine.  However, if the aar file is updated, the state goes to active.  I would think in this case it should still be inactive.

  was:Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.


> Exploded POJO service always activated even if deactivated from ADMIN console
> -----------------------------------------------------------------------------
>
>                 Key: AXIS2-2567
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2567
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: nightly
>            Reporter: nadir amra
>
> Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.
> For aar files, this seems to work fine.  However, if the aar file is updated, the state goes to active.  I would think in this case it should still be inactive.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Assigned: (AXIS2-2567) Service activation with hotupdate not correct

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

Deepal Jayasinghe reassigned AXIS2-2567:
----------------------------------------

    Assignee: Deepal Jayasinghe

> Service activation with hotupdate not correct
> ---------------------------------------------
>
>                 Key: AXIS2-2567
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2567
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: nightly
>            Reporter: nadir amra
>         Assigned To: Deepal Jayasinghe
>
> Running with latest build.  hotupdate set to "true" in axis2.xml.  An exploded POJO service is deployed and AXIS2 engine activates the service.  From the ADMIN console, deactivate the service.  If you click on the  "Available Services" link you will find the service still active.
> For aar files, this seems to work fine.  However, if the aar file is updated, the state goes to active.  I would think in this case it should still be inactive.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org