[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-bpel] Formated minutes of the 20080110 concall
Because of the incorrect logo included in the formated minutes (sent in the last email) there were rumors of this TC being a renegade TC and attaching itself to a different organization. To dispel these rumor I have attached the formatted minutes with the correct organization's logo. -Anish --Title: OASIS SCA BPEL TC Teleconference -- 10 Jan 2007
<anish> Scribe: Dieter Koenig
<anish> ScribeNick: DieterKoenig
1. Roll Call http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/roster.php
agenda accepted
minutes of 2007/12/13 approved
no pending action items
no new issues since last call
next agenda item: issues
issue 11 - http://www.osoa.org/jira/browse/BPEL-11
clarification sent to mailing list - see mail from mike edwards
<anish> http://lists.oasis-open.org/archives/sca-bpel/200712/msg00042.html
<anish> If a BPEL variable that is used as a property has an initialization from-spec then mustSupply="false" must be specified on the component type property declaration. If the variable has an initialization 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 initialization from-spec is not evaluated.
<anish> If the from-spec is a literal value, where it has the following form>
<anish> <from><literal>literal value</literal></from>
<anish> then the literal value will be represented as the default value in the component type for the process. Any other kind of initialization from-spec will not be represented in the component type. However, even though the other kinds of initialization from-spec are not represented in the component type, they would still be computed and used as the default value for the property when the component does not provide a value for that property.
mark ford: bpel is treated differently than java
mark ford: alternatively, one can do bpel initialization first, then modify values using properties
<anish> Date: 10 Jan 2007
mark ford: when should the property assignment take place: before/during/after bpel variable init
scribe: to be consistent with java, it should be after variable init
<anish> mike's wording: "The componentType of a component MAY contain a default value for any property which has a default value that is NOT represented in the componentType. "
alex yiu: bpel implementation and component type may get out of sync
mike rowley: according to the assembly spec, component types must remain "compatible"
mike rowley should sca-asm open an issue in order to define "compatibility"
<scribe> ACTION: item to open an issue in sca-asm
action item for mike rowley -- open sca-asm issue for defining "compatibility"
<anish> ACTION: mikeR to open an issue regarding agreement of default values in the CT file and the runtime
mike rowley: move to resolve issue 11 with the proposed wording
<anish> ACTION: mikeE to open an issue regarding whether default values in the runtime are necessarily represented in the CT file
mark ford: change wording to reflect the point in time of the sca property assignment to a bpel variable
<anish> Here is the proposal again in full:
<anish> If a BPEL variable that is used as a property has an initialization from-spec then mustSupply="false" must be specified on the component type property declaration.
<anish> If the variable has an initialization 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 initialization from-spec is not evaluated.
<anish> If the from-spec is a literal value, where it has the following form>
<anish> <from><literal>literal value</literal></from>
<anish> then the literal value will be represented as the default value in the component type for the process. Any other kind of initialization from-spec will not be represented in the component type. However, even though the other kinds of initialization from-spec are not represented in the component type, they would still be computed and used as the default value for the property when the component does not provide a value for that property.
<anish> If a BPEL variable that is used as a property has an initialization from-spec then mustSupply="false" must be specified on the component type property declaration
alex yiu: by default, bpel uses xpath as expression language which is side-effect free
(one may have other expr languages in bpel)
alex yiu: bpel variables are marked explicitly as being init'd by sca properties
<MichaelRowley> Possible new form for the relevent sentence: "If a value is provided for the property, the initialization from-spec MUST be evaluated, but the value of the variable will be changed to the value specified for the property on the component immediately after the initialization is evaluated (before any following variable initialization from-spec is evaluated)."
<MichaelRowley> If a BPEL variable that is used as a property has an initialization from-spec then mustSupply="false" must be specified on the component type property declaration.
<MichaelRowley> If the variable has an initialization 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 initialization from-spec MUST be evaluated, but the value of the variable will be changed to the value specified for the property on the component
<MichaelRowley> If the from-spec is a literal value, where it has the following form>
<MichaelRowley> <from><literal>literal value</literal></from>
<MichaelRowley> then the literal value will be represented as the default value in the component type for the process. Any other kind of initialization from-spec will not be represented in the component type. However, even though the other kinds of initialization from-spec are not represented in the component type, they would still be computed and used as the default value for the property
<MichaelRowley> If a BPEL variable that is used as a property has an initialization from-spec then mustSupply="false" must be specified on the component type property declaration.
mike rowley: (immediate replacement is different from java but fits better with bpel)
mike rowley: moves to accept resolution for issue 11 with the modified wording (removing the first sentence which is duplicate)
alex yiu: seconds
issue 11 resolved without objection
<anish> ACTION: MikeR to incorporate issue 11 resolution in the spec
next agenda item
Issue 2 http://www.osoa.org/jira/browse/BPEL-2
mike rowley: sca-bpel should specify *how* component types side files are located
anish: component type is tightly coupled to an implementation
<continue discussion on mailing list and in next week's call>
AOB?
meeting adjourned
<anish> ACTION: MikeR to start an email discussion on issue 2, especially the distinction between 'how' a CT side is located v. 'where' it is located
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]