[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-bpel] Issue 11 - BPEL variable initialization and SCA properties
I looked at the Property section of the Assembly Specification. It
looks like what is there is OK. Here it is: mustSupply (optional) – whether the
property value must be supplied by the component that uses the implementation
– when mustSupply="true" the component must supply a value
since the implementation has no default value for the property. A default-property-value
should only be supplied when mustSupply="false" (the default setting for
the mustSupply attribute), since the implication of a default value is that it
is used only when a value is not supplied by the using component. It says that a default value should be only be supplied when mustSupply
is false, but it _doesn’t_
say that a default value MUST be supplied. Perhaps we could add the following to the SCA BPEL spec at line 357 (in
the paragraph that describes the meaning of sca:property=”yes”): “If the variable has an initialization expression (a from-spec) then that becomes the default
value for the variable in cases where the SCA component does not provide a
value for that property. If a value is
provided for the property, the expression is not evaluated. If the
from-spec is a literal value, where it has the following form: <from><literal>literal value</literal></from> then the literal value will be represented as the default value in the component
type for the process. Any other kind of initialization expression will
not be represented in the component type.” Michael -----Original Message----- Issue entered. http://www.osoa.org/jira/browse/BPEL-11 Regards, Alex Yiu Mark Ford wrote: > TARGET: SCA Client and Implementation Model Specification for
WS-BPEL > > TITLE: BPEL variable initialization and SCA properties > > DESCRIPTION: Is the target variable allowed to have an
initialization > defined within the BPEL process and if so, is this initialization
ignored? > It seems like the initialization should be allowed but not
executed in the > case where a process is packaged as an SCA and the property is
provided by > the component. It's probably also worth pointing out that the
variable must > be an element or type variable. Message variables cannot be
initialized by > an SCA property. > > > |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]