[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
