Issue 9567: BPEL->BPMN mapping problem correlation set (bpmn-ftf) Source: Capability Measurement (Mr. Karl Frank, Karl.Frank@ngc.com karl.frank@ngc.com karl.karolus@gmail.com karl.frank@capabilitymeasurement.com) Nature: Uncategorized Issue Severity: Summary: variables having 'message' type are imported as property sets, reference to message type is lost - it is hard to model variable as input and assign result of <invoke> to variable. If passing arguments can be modeled as sequence of assignments, receive part is impossible to model clearly--assignment is not symmetric, from is expected to be an expression and there is no way to define reference to service call result in expression as BPEL don't need it Resolution: Revised Text: Actions taken: April 13, 2006: received issue Discussion: Defer: While the Issue may be valid, it represents potentially significant modifications. Thus, this Issue will be deferred and handled by work on a later version of BPMN. End of Annotations:===== s is issue # 9567 BPEL->BPMN mapping problem(s) variables having 'message' type are imported as property sets, reference to message type is lost - it is hard to model variable as input and assign result of to variable. If passing arguments can be modeled as sequence of assignments, receive part is impossible to model clearly--assignment is not symmetric, from is expected to be an expression and there is no way to define reference to service call result in expression as BPEL don't To: bpmn-ftf@omg.org Subject: Proposed Resolution for Issue 9567 X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 From: Stephen A White Date: Fri, 10 Nov 2006 21:43:22 -0800 X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.1HF346 | August 4, 2006) at 11/10/2006 22:43:23, Serialize complete at 11/10/2006 22:43:23 This is intended for Ballot 5 (the first ballot of the FTF V2) Issue 9567: BPEL->BPMN mapping problem Description: variables having 'message' type are imported as property sets, reference to message type is lost. It is hard to model variable as input and assign result of to variable. If passing arguments can be modeled as sequence of assignments, receive part is impossible to model clearly--assignment is not symmetric, from is expected to be an expression and there is no way to define reference to service call result in expression as BPEL don't need it Suggested Resolution: Defer: While the Issue may be valid, it represents potentially significant modifications. Thus, this Issue will be deferred and handled by work on a later version of BPMN. Revised Text: None need it