Bug 986760 - XmlBPMNProcessDumper.dump() misses conditionExpression in sequenceFlow
Summary: XmlBPMNProcessDumper.dump() misses conditionExpression in sequenceFlow
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 5.x.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER2
: 6.0.0
Assignee: Marco Rietveld
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-22 03:22 UTC by Toshiya Kobayashi
Modified: 2018-12-03 19:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 985864
Environment:
Last Closed: 2014-08-06 20:08:26 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPM-4069 0 Major Resolved XmlBPMNProcessDumper.dump() misses conditionExpression in sequenceFlow 2015-05-25 13:34:54 UTC

Description Toshiya Kobayashi 2013-07-22 03:22:48 UTC 
+++ This bug was initially created as a clone of Bug #985864 +++

Description of problem:

Platform BZ for https://issues.jboss.org/browse/JBPM-4069


Steps to Reproduce:
1. Create bpmn which includes SplitNode with conditionExpression in sequenceFlow
2. Parse the bpmn with KnowledgeBuilder
3. call XmlBPMNProcessDumper.dump() and compare original and generated xml

Actual results:

generated xml misses conditionExpression (See JBPM-4069)

Expected results:

generated xml doesn't miss conditionExpression
Comment 1 Toshiya Kobayashi 2013-07-22 03:29:03 UTC 
As mentioned in BZ985864 , this has been fixed in master so it's okay to move to MODIFIED.
Comment 2 Marek Baluch 2013-09-09 11:43:32 UTC 
Verified on ER2.

Dump snipp.

<conditionExpression xsi:type="tFormalExpression" language="http://www.java.com/java" >return 1==(Integer)kcontext.getVariable("myVar");</conditionExpression>

<conditionExpression xsi:type="tFormalExpression" language="http://www.java.com/java" >return 1&gt;=(Integer)kcontext.getVariable("myVar");</conditionExpression>
Comment 6 Tomas Livora 2014-08-05 12:38:41 UTC 
http://git.app.eng.bos.redhat.com/git/jbossqe/brms.git/commit/?h=6.0.x&id=9d9353e4dc814aedb35282a2f3333fb901699e18
Note You need to log in before you can comment on or make changes to this bug.