[jira] Commented: (ODE-568) Undeploying a process does not remove corresponding service from ODE axis2

["Alexis Midon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694809#action_12694809 ] 

Alexis Midon commented on ODE-568:
----------------------------------

It appears we don't need the unique name introduced by ODE-345 as the key of the service map.

Actually, if a service is shared by multiple processes (i.e. <enableSharing/> set in deploy.xml), only one single instance of ODEService is created. [1]
In other cases, the assumption that different processes hava different service name/port name is valid.

So {service name, port name} is a valid key for the service map.


[1] http://fisheye6.atlassian.com/browse/ode/branches/APACHE_ODE_1.X/bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelProcess.java?r=APACHE_ODE_1.X#l561

> 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
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>
> 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.