[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue - 112 - Input/Output Elements on Messaging Activities
Hello,
I am
not sure how that Makro will work (i.e. how will it look like in the spec?),
However I agree with the general problem and have to add some aditional
arguments:
not
only the temporary variable is needed, but also the assigns, which may be placed
anywhere in the control flow. This is very hard for a modelling tool to read a
bpel and understand the intention of the modeller, when the assign is not
sequenced/linked directly before the invoke. I.e. for graphical notations like
BPMN which do not support data mapping activities, but do parameter assignments
with properties, it is not safe for them display an assign as the param
population belonging to the activity in question. In fact the temporary variable
encourages its reuse and therefore destroys the optimization of hiding the
assign in the properties sheet of the invoke.
So an
assign fro mvariables to invoke as a syntactic change would allow a clearer
expression of intent.
Mit freundlichen Grüßen
Bernd Eckenfels Chief Architect -- SEEBURGER AG - Edisonstr.1 , D-75015 Bretten, Germany Fax: +49 (0)7252 96-2400 - Phone: +49 (0)7252 96-1256 mailto:b.eckenfels@seeburger.de - http://www.seeburger.de
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]