[
https://issues.apache.org/jira/browse/ODE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Zenzin updated ODE-700:
----------------------------
Attachment: ode-700.patch
Attached ode-700.patch is patch which changes the logic for process retire upon
deployment of a new version: now it does not rely on incremental nature of
version number. It simply tries to spot _any_ existing version of the same
deployment unit and retire it before it deploys a new version.
> deploy retires the oldest package, not the active one
> -----------------------------------------------------
>
> Key: ODE-700
> URL: https://issues.apache.org/jira/browse/ODE-700
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.2, 1.3.2, 1.3.3
> Reporter: Alexis Midon
> Attachments: ode-700.patch
>
>
> org.apache.ode.bpel.pmapi.ProcessManagement#setPackageRetired does not retire
> all the active processes of previous package versions. Only the previous
> version (n-1) is retired.
> Considering that the ProcessManagement API allows to activate the version n-2
> of a process, you can end up with 2 active versions of a given process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
