You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2009/12/14 18:25:18 UTC
[jira] Reopened: (ODE-700) deploy retires the oldest package, not
the active one
[ https://issues.apache.org/jira/browse/ODE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen reopened ODE-700:
----------------------------------
The fix breaks a few test cases.
On 1.x:
# org.apache.ode.test.VersionedRedeployTest.testRetireOld
# org.apache.ode.jbi.RetireJbiTest.testRetire
On trunk:
# org.apache.ode.test.VersionedRedeployTest.testRetireOld
> 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
> Assignee: Alexis Midon
> Fix For: 1.3.4
>
> 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.