Minutes
agenda bashing
<Dave Booz>
agenda approved w/o
AI
Liason to testing
<Dave Booz>
Sanjay notes that Assembly TC has a subcommittee that is doing some work on this, consistency across TCs would be a good thing
<Mike Edwards>
Specific testing work will be required for the BPEL spec - so someone or some group of people from this TC need to take part
<Dave Booz>
Mike R suggests that Anish and/or Mike E could be BPEL TC reps, Anish volunteered
<Mike Edwards>
Be warned that I will probably spend most of my effort on the Assembly testing
Issue 22
<Dave Booz>
proposal in JIRA
<anish>
this is issue 36 in assembly
<Dave Booz>
discussion of two pieces of this issue
<anish>
the resolution text was to replace the text in section 4.1 with the following:
<anish>
Component type represents the configurable aspects of an implementation.
A component type consists of services that are offered, references to
other services that can be wired and properties that can be set. The
settable properties and the settable references to services are
configured by a component that uses the implementation.
An implementation type specification (for example, the WS-BPEL Client
and Implementation Specification Version 1.1 [ref]) specifies the
mechanism(s) by which the component type associated with an
implementation of that type is derived.
Since SCA allows a broad range of implementation technologies, it is
expected that some implementation technologies (for example, the Java
Client and Implementation Specification Version 1.1 [ref]) allow
for introspecting the implementation artifact(s) (for example, a Java
class) to derive the component type information. Other implementation
technologies might not allow for introspection of the implementation
artifact(s). In those cases where introspection is not allowed, SCA
encourages the use of a SCA component type side file. A component type
side file is an XML file whose document root element is
sca:componentType.
The implementation type specification defines
whether introspection is allowed, whether a side file is allowed, both are
allowed or some other mechanism specifies the CT.
The component type information derived through introspection is
called the 'introspected component type'. In any case, the implementation
type specification specifies how multiple sources of information
are combined to produce the 'effective component type'. The effective
component type is the component type metadata that is
presented to the using Component for configuration.
The extension of a componentType side file name MUST be
.componentType. The name and location of a componentType side file, if
allowed, is defined by the implementation type specification.
If a component type side file is not allowed for a particular
implementation type, the effective component type and introspected
component type are one and the same for that implementation type.
For the rest of this document, when the term 'component type' is used it refers to the 'effective component type'.
<Dave Booz>
it is noted that resolution of assembly 36 needs to be handled by each C&I, Anish is raising an issue in this TC during the
meeting
<anish>
fine with what MikeR is proposing
<Dave Booz>
discussion on the value of keeping interface.partnerLinkType given that assembly didn't accept it
<Dave Booz>
Mike R proposes that we remove the concept, there is some sympathy with the idea
<Dave Booz>
motion: Mike R - resolve issue 22 by removing the concept of interface.partnerLinkType from the spec
<Dave Booz>
second: Danny
Resolution: Issue 22 resolved w/o
Issue 18 - RFC2119 language
<Dave Booz>
Michael walks the TC through the document
<Dave Booz>
discussion on line 52 - "The component type MAY be generated..."
<Dave Booz>
Mike R suggests to strike the line - it is stricken
<Dave Booz>
discussion on line 120-
<Michael Rowley>
The role that the partner link specified as myRole MUST correspond to the WSDL port type of the service in the introspected
component type.
<Michael Rowley>
The port type of the myRole of the partner link MUST be the same as the WSDL port type of the <interface.wsdl> declaration
for the service in the introspected component type.
<Michael Rowley>
The WSDL port type in the <interface.wsdl> declaration for the service in the introspected component type MUST be the same
as the port type of the myRole of the partner link.
<Michael Rowley>
...same QName as...
<Dave Booz>
replace lines 119-121 with new sentence above (exclude QName suggestion)
<Dave Booz>
discussion on lines 154-155
<Michael Rowley>
If the partner link type has two roles, then the <interface.wsdl> declaration MUST also have a @callbackInterface attribute
whose value is the same as the partnerRoles WSDL port type.
<anish>
If the partner link type has two roles, then the <interface.wsdl> declaration MUST also have a @callbackInterface attribute
whose value points to the same WSDL port type as the partnerRole.
<Dave Booz>
Anish's change is accepted
<Michael Rowley>
Walk-through stopped in section 2.2. Continue next meeting with 2.3.
<Dave Booz>
stopped walkthrough at 2.2 and will continue at section 2.3
Approval of minutes
Resolution: minutes of 2008-10-23 telecon accepted w/o
<Dave Booz>
meeting adjourned
Schreiber diagnostics output
[Delete this section before publishing the minutes]
statistics: Schreiber found 119 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 59: Dave Booz: s/basing/bashing
edits: Line 174: Dave Booz: s/121-122/154-155
command-scribe: Line 15: Dave Booz recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 20: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 28: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 31: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 47: Check for possible unrecognized nick 'Latest proposal'
command-scribe: Line 55: Dave Booz recognized
command-scribe: Schreiber detected that this section was scribed online
edit-substitute: command on line 59 succeeded, changed line 57 from 'basing' to 'bashing'
edit-delete: Line 59 was deleted
citation-detection-irc1: Line 110: Check for possible unrecognized nick 'sca'
edit-substitute: command on line 174 succeeded, changed line 170 from '121-122' to '154-155'
edit-delete: Line 174 was deleted
system: Transformer: SAXON 9.0.0.2
[End of Schreiber diagnostic output]