Hide Forgot
Date of First Response: 2008-12-12 08:16:19 project_key: SOA See JBPM-1771
Link: Added: This issue depends JBPM-1918
The jpdl-3.2.2-SOA-4.2.0.CP03 code base does not have an owner. The SOA-P should update to jbpm-3.3.0.GA
The platform does not (yet) contain jBPM 3.3.*. When/if it does, we will verify this bug as fixed.
ok,cd jb then we need to sort out the resource issues we have with that code base first. I'll follow up with Marc. The current SOA-4.2 branch is however already based on jbpm-3.3.x https://svn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.3.x-SOA-4.2
No soa builds are based on jbpm-3.3.x at the moment. We cannot move to 3.3 until it is proven to be backwardly compatible for soa purposes.
Doesn't look like we're going to sort this for CP03 so I've move it up to CP04
Remember that 3.2.4 = 3.3.0 and 3.2.5 = 3.3.1, with the sole difference of the GWT-console. JBPM-1918 / JBPM-1771 are resolved as of 3.2.4.
Link: Added: This issue depends JBPM-1771
Link: Removed: This issue depends JBPM-1918
JBPM-1771 has been fixed since jBPM 3.2.4 and shipped with SOA-P 4.3 CP01 and 4.2 CP04. I'm setting 4.3 CP03 and 4.2 CP05 as the fix versions so that this issue appears in the release change log.
Draft text for the Resolved Issues section of Release Notes states: https://jira.jboss.org/jira/browse/JBPM-1771 The JobExecutorDBTest would return incorrect results for Postgres and Oracle databases. This was due to an outdated version of jBPM being included with the software. An upgrade of jBPM to version 3.2.4 has corrected this bug.
Verified in ER1