ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexis Midon (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (ODE-568) Undeploying a process does not remove corresponding service from ODE axis2
Date Thu, 10 Sep 2009 16:41:59 GMT

     [ https://issues.apache.org/jira/browse/ODE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexis Midon reopened ODE-568:
------------------------------


The committed fix revealed an issue: now that org.apache.ode.bpel.iapi.BindingContext#deactivateMyRoleEndpoint
uses the right key to deactivate an endpoint, it appears that the undeployment of a retired
process deactivates the endpoint of the active version of the same process.

org.apache.ode.bpel.engine.BpelProcess#deactivate must invoke BindingContext#deactivateMyRoleEndpoint
 only if the process is ACTIVE.

> Undeploying a process does not remove corresponding service from ODE axis2
> --------------------------------------------------------------------------
>
>                 Key: ODE-568
>                 URL: https://issues.apache.org/jira/browse/ODE-568
>             Project: ODE
>          Issue Type: Bug
>          Components: Axis2 Integration
>    Affects Versions: 1.3.2
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3.2
>
>
> Undeploying a process does not remove corresponding service from axis2
> You can see that webservice in Axis2 service list view.
> http://localhost:8080/ode/axis2-admin/listService
> It requires login. Default login details: admin/axis2 

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


Mime
View raw message