Date of First Response: 2008-10-01 07:32:01 project_key: SOA
Link: Added: This issue depends JBPM-1447
Link: Added: This issue depends JBPM-1448
Link: Added: This issue depends JBPM-1439
Link: Added: This issue depends JBPM-1440
Link: Added: This issue depends JBPM-1441
Link: Added: This issue depends JBPM-1442
Link: Added: This issue depends JBPM-1443
Link: Added: This issue depends JBPM-1444
Link: Added: This issue depends JBPM-1445
Link: Added: This issue depends JBPM-1446
Link: Added: This issue depends JBPM-1450
Link: Added: This issue depends JBPM-1451
Link: Added: This issue depends JBPM-1449
Link: Removed: This issue depends JBPM-1442
Link: Removed: This issue depends JBPM-1440
Link: Removed: This issue depends JBPM-1447
Link: Added: This issue depends JBPM-1404
TomB is the owner of SOA issues related to the jBPM3 code base
Link: Added: This issue depends SOA-699
Link: Removed: This issue depends SOA-699
Link: Added: This issue related SOA-844
Emailed Tom Baeyens for comments
Link: Added: This issue is related to SOA-646
Link: Removed: This issue depends JBPM-1451
Fixed in jbpm-3.3.0.GA
At least JBPM-1446 display non GMT+0 time zones was not fixed Process 49 Ended Mar 6, 2009 10:13:53 AM Mar 6, 2009 10:13:57 AM Client time 11:15 Server time 11:15 Location GMT+1
I went through the list of dependent issues and found the following anomalies: JBPM-1446 is in 3.2.6.GA, but not 3.2.5.SP3 JBPM-1449 was simply resolved as "out of date" These other issues seem done, but the SOA-P team did not confirm. JBPM-1443 has an unclear resolution JBPM-1444 was resolved as duplicate of JBPM-1071
Release Notes: Not being documented JBPM-1446 - JBPM-1446 is in 3.2.6.GA, but not 3.2.5.SP3 JBPM-1449 - JBPM-1449 was simply resolved as "out of date" JBPM-1441 - fixed sybase test failures JBPM-1439 - internal JBPM-1450 - Already documented as known issue Documented: JBPM-1404 - documented as per https://jira.jboss.org/jira/browse/SOA-649 JBPM-1448 - documented as per https://jira.jboss.org/jira/browse/SOA-648 JBPM-1443 - Restored namespace reference in the bpm_orchestraton1 quickstart JBPM-1444 - as JBPM-107 - Fixed issue with concurrent signalling from multiple threads when using jBPM with MySQL on Linux JBPM-1445 - FIXED: the jBPM 'websale sample application was crashing when approving orders.
Current status in CR4: JBPM-1449 - message as no longer ERROR but INFO
You mean JBPM-1449 is fixed already? How was it fixed, was the facelets dependency upgraded?
Well, in SOA-P 4.3 CP01 there is a new version of JSF - maybe this is the reason...
Link: Added: This issue depends JBPM-2112
JBPM-1446 has been ported to 3.2.5.SP4 JBPM-1449 does not apply to 3.2.5.SP4 as the jsf-facelets version has been upgraded in SOA-P jBPM 3.2.5.SP4 is tagged and published to the maven repo - JBPM-2112
Need to integrate into the change of console into the platform.
Fixed with revision 2838 (4.3 branch) of: build-tools/dependencies.properties build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app/t_tokens.xhtml build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app/t_comments.xhtml build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app/t_tasks.xhtml build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app/t_processinstances.xhtml build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app/jobs.xhtml build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app/token.xhtml build-tools/builders/soa/p-consoles/jbpm/resources/overlays/app/task.xhtml Commit message: SOA-647 Update jBPM to 3.2.5 SP4. Add additional JSF console overlays from 3.2.6 SP2 to fix JBPM-1446.
Verified in CR5