Hide Forgot
++ This bug is a clone of bug 779543 ++ Affects: Release Notes Date of First Response: 2010-02-25 15:16:42 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/446713 Workaround: Workaround Exists Workaround Description: Write condition as element text. <decision name="node1"> <transition to="node2"><condition>#{AAA == null}</condition></transition> <transition to="node3"></transition> </decision> project_key: SOA Platform issue for JBPM-2784: schema doesn't accept condition attribute in transition
Workaround Description: Added: Write condition as element text. <decision name="node1"> <transition to="node2"><condition>#{AAA == null}</condition></transition> <transition to="node3"></transition> </decision> Workaround: Added: [Workaround Exists]
Link: Added: This issue incorporates JBPM-2784
Approved for SOA 4.3 CP03.
JBPM-2784 is resolved. SOA-P team, please close as you see fit.
Draft text for Resolved Issues section of Release Notes states: https://jira.jboss.org/jira/browse/JBPM-2784 Process definitions with condition attributes such as "#{AAA == null}" were being rejected by the Schema. This caused org.jbpm.jpdl.JpdlException: [[ERROR] cvc-complex- type.3.2.2: Attribute 'condition' is not allowed to appear in element 'transition'. exceptions. To fix this problem, the ability to handle condition attributes has been added to the transition element in the jPDL 3.2 Schema. As a result, they are no longer rejected by the Schema.
Verified in 4.3.CP03 ER1