Red Hat Bugzilla – Bug 812006
jBPM5 does not handle timer definitions conforming to ISO-8601
Last modified: 2012-11-04 19:59:05 EST
Description of problem:
BPMN 2.0 requires that timeCycle and timeDuration conform to the ISO-8601
format for time interval representations.
Version-Release number of selected component (if applicable):
Reproducible with reccuring time intervals beginning with 'Rnn/' and itervals that use time durations, which are required to start with 'P'
Steps to Reproduce:
Using an ISO-8601 compliant time interval expression may result with an exception similar to
> org.drools.RuntimeDroolsException: Error parsing time string: [ R/P10S ]
jBPM engine should be able to handle all time interval expressions that conform to ISO-8601 and interpret them correctly
Resolving this issue would allow for implementing CRON timers requested in https://issues.jboss.org/browse/JBPM-2889
Created attachment 577077 [details]
server.log with the related exception
jBPM5 is currently using it's own legacy format for expressing timer duration and cycle. Although the BPMN2 specification seems to require the use of ISO-8601 in certain locations, the timer properties are actually expressions, and formal expressions have a language attribute, so different languages for supporting timers are technically still possible.
While jBPM5 currently only supported the legacy format, we will be looking at adding support for IS0-8601 expressions in the future.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The BPMN 2.0 specification requires that timeCycle and timeDuration conforms to the ISO-8601 for time interval representations, however, jBPM5 is currently using it's own legacy format for expressing timer duration and cycle.
*** Bug 833394 has been marked as a duplicate of this bug. ***