Hide Forgot
++ This bug is a clone of bug 779624 ++ Date of First Response: 2010-05-18 12:49:33 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/610413 project_key: SOA Platform issue for JBPM-2828
Linking project issue.
Link: Added: This issue depends JBPM-2828
Link: Added: This issue is related to SOA-1956
Resolving since project issue JBPM-2828 and related issue SOA-1956 are both resolved already. Set the same fix version as SOA-1956, 5.0.2. If you reopen, please reassign appropriately.
Verified in CR1
More info needed for 5.0.2 release notes: are the following statements true, and what should ??? be below ContextInstance.deleteVariable(name) did not actually delete variables from the database, the VariableContainer.deleteVariable() method instead removed references to the process execution. This could lead to orphaned records in the database. ??? now removes the variables from the database if the logging service is disabled. If logging is enabled the new VariableDeleteLog holds a reference to the variable and it is removed when the process instance is deleted.
Added to SOA 5.1 Release Notes as resolved: JBPM-2828 ContextInstance.deleteVariable(name) was not actually deleting variables from the database, and instead only removed references to the process execution. This could lead to orphaned records in the database. This method now removes the variables from the database if the logging service is disabled. If logging is enabled the new VariableDeleteLog holds a reference to the variable and it is removed when the process instance is deleted.
Link: Added: This issue is duplicated by SOA-2208