You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2010/04/14 00:02:01 UTC
[jira] Resolved: (ODE-571) Instance work done within newest process
version after receiving request to a retired instance
[ https://issues.apache.org/jira/browse/ODE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin resolved ODE-571.
-----------------------------
Resolution: Fixed
> Instance work done within newest process version after receiving request to a retired instance
> ----------------------------------------------------------------------------------------------
>
> Key: ODE-571
> URL: https://issues.apache.org/jira/browse/ODE-571
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.2
> Reporter: Rafal Rusin
> Assignee: Rafal Rusin
> Fix For: 1.3.4
>
> Attachments: executeInstanceInProperProcessVersion.diff
>
>
> I did following:
> 1. deployed process X version 1
> 2. started instance A
> 3. deployed process X version 2
> 4. continued instance A
> 5. instance A tried to read external variable, but it caused error, because it took definition from X version 2
> I did some investigation and saw that in PartnerLinkMyRoleImpl.java, there is a runtime context created for my role partner link, which points to process X version 2.
> I did a patch, which took BpelProcess object from process instance's dao for execution and this solved problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira