SCA-J Conference Call–14thFebruary2011

Attendees:

David BoozIBMGroup Member

Mike EdwardsIBMGroup Member

Bryan AupperleIBMGroup Member

Anish KarmarkarOracle CorporationGroup Member

Martin ChapmanOracle CorporationGroup Member

Decisions:

-Minutes for 2011-02-07accepted

-JAVA-225 Resolved

Issue Status:

Open: 11

Opened Today: 0

Resolved Today:1

Closed Today: 0

Closed No Action Today:0

Actions:

20110214-01: (Anish)followup with Robin wrt version number in filename for POJO test case doc

20110214-02: (Anish) followup with TC-ADMIN wrt zip reference "update" on coverpage of the TC specs

20110214-03: (Anish) write an outline for spec/assertions/test case conformance and inter-dependency

Raw Chat log:

[11:02]anish: Agenda --

[11:02]anish: 1. Roll call

2. Scribe appointment

Scribe list attached below

3. Agenda bashing

4. Meeting Minutes

Minutes of 2011-02-07 telcon

5. TC Administrivia

a. Recording issue status - 11 open, 0 new

b. Filenames for POJO test case and test assertion docs

c. Updating cover page of the POJO TC spec

6. ACTION ITEMS

2010-11-15-02: Mike to follow up with Jacques on 217, 218, ,219, 220, and 221

PENDING

20101206-02: (Mike) Post a comment to the list with a strawman proposal for Issue 224

PENDING

20110124-02: (Anish) Take up the Links question relating to JAVA-227 with TC-Admin - aim to get the links updated without requiring a new CSD or public review

DONE

20110207-01: Anish to send a proposal to resolve 225

DONE

7. New Issues (requires 2/3)

NONE

8. Issues with proposals

a. JAVA-225 Ambiguity about the implicit reference interface in the introspected component type of a Spring app context

Proposal:

b. JAVA-227: TAB comments on POJO CI TCs

9. Issues waiting for updated proposals (Spring/EJB/JEE)

a. JAVA-217 Weak design: Target is often not well identified, in several TAs

b. JAVA-220 Target should not be an "event", but an identifiable entity

c. JAVA-221 Stronger use of "tags" might help classify TAs based on targets

d. JAVA-225 Ambiguity about the implicit reference interface in the introspected component type of a Spring app context

e. JAVA-109: Property and reference names computed from SCA annotations in web modules not specified explicitly

Proposal in Jira

Waiting for updated proposal (Vamsi)

f. JAVA-174: Consider portlets in the SCA JEE specification

h. JAVA-91: Java EE Spec: Need to define the derivation of the name of a component contributed to the Domain by an application.composite file

Waiting for updated proposal (Mike)

i. JAVA-93: JEE Integration spec needs to define how effective CT is calculated

Waiting for updated proposal (Anish)

j. JAVA-108: RFC2119 Language is needed for the SCA-JEE Specification

Waiting for updated proposal

k. JAVA-88: Java EE Spec: The @archive attribute of the implementation.jee element needs fixing

No proposal

Plamen to check whether on his informal JEE issues list

10. AOB

a. straggler role

11. Spec status

CAA (part of 1st batch of 1.1 specs):

2 new issue, 2nd PR ended 2010-12-08, CSD05 expected to be final CSD

1st impl: Tuscany (compliant), 2nd impl: ??

CD01 PR ended 2010-10-24, 0 open issue, CSD02 expected to be final CSD

TC: CD01 PR ended 2010-10-24, 0 open issue, CSD02 expected to be final CSD

POJO (part of 1st batch of 1.1 specs):

0 open issues, 2st PR ended 2010-12-08, CSD03 expected to be final CSD

1st impl: Tuscany (compliant), 2nd impl: ??

TA: CSD01 PR ended 2010-12-23

TC: CDS01 PR ended 2010-12-23

EJB Binding (not part of 1st batch of 1.1 specs):

0 open issues, 1st PR done, CSD03 expected to be final CSD

1st impl: ??, 2nd impl: ??

TA: WD stage, no CSD yet, 60 day PR needed

TC: WD stage, no CSD yet, 60 day PR needed

Spring C&I (not part of 1st batch of 1.1 specs):

1 open issues, WD stage, no CSD yet, 60 day PR needed

1st impl: ??, 2nd impl: ??

TA: no work done

TC: no work done

JEE (not part of 1st batch of 1.1 specs):

6 open issues, WD stage (not actively worked on), no CSD yet, 60 day PR needed

1st impl: ??, 2nd impl: ??

TA: no work done

TC: no work done

[11:06]MartinC: scribe: MartinC

[11:07]MartinC: topic: agenda bashing

[11:07]MartinC: Approved as posted

[11:07]MartinC: topic: Meeting Minutes

Minutes of 2011-02-07 telcon

[11:07]MartinC: approved w/o

[11:08]MartinC: topic: tc admin

[11:08]MartinC: 11 open issues

[11:10]MartinC: ACTION: Anish to followup with Robin wrt version number in filename for POJO test case doc

[11:11]MartinC: Updating cover page of the POJO TC spec: Robin's reading of the TC Process is that adding a link to related work would require another PR

[11:12]anish:

[11:15]MartinC: Martin notes that this could be considered an update, albeit to an empty reference, though its clear these are part of the work product.

[11:17]MartinC: Mike E: should be considered an correction/update to front matter

[11:17]MartinC: s/an/a

[11:19]MartinC: a 15 day PR might be quicker than an appeal

[11:23]MartinC: Bryan, the zip file was sent with the document for the PR, so the references between them were implicit so updating the cover page to make explicit is within scope of tc process. However a quick turn around is the preferred approach.

[11:24]MartinC: Anish: similar position and can point out to Robin that most of the checks have already been done so should not take ages to publish.

[11:25]MartinC:Bryan: we need a new document to vote on with the reference to the zip on the cover page

[11:25]MartinC: by next week we should know Robin's view

[11:26]MartinC: Action: Anish to followup with TC-ADMIN wrt zip reference "update" on coverpage of the TC specs

[11:28]MartinC: topic: Action Items

[11:28]MartinC: 2010-11-15-02: Mike to follow up with Jacques on 217, 218, ,219, 220, and 221

[11:28]MartinC: Done

[11:28]MartinC: 20101206-02: (Mike) Post a comment to the list with a strawman proposal for Issue 224

Done

[11:29]MartinC: 20110124-02: (Anish) Take up the Links question relating to JAVA-227 with TC-Admin - aim to get the links updated without requiring a new CSD or public review

DONE

20110207-01: Anish to send a proposal to resolve 225

DONE

[11:29]MartinC: topic: issue discussion

[11:29]MartinC: JAVA-227: TAB comments on POJO CI TCs

[11:29]MartinC: agreed to add link to the zip file under related work

[11:31]MartinC: Anish: propose that we add conformance text that says to conform to the test cases, pass the tests

[11:34]MartinC: Anish also proposes that the specs include in their conformance that the test cases must be passt (and no other test case)

[11:35]MartinC: this would be in the main spec

[11:47]MartinC: Anish: is it worthwhile putting out a proposal for the right way to do this?

[11:48]MartinC: MikeE: yes but keep lanauages in conformance sections very simple

[11:48]MartinC:Bryan: corresponding discussions will probably be required in Bindings and Policy

[11:49]MartinC: ACTION: Anish to write an outline for spec/assertions/test case conformance and inter-dependency

[11:49]MartinC: Issue 225

[11:50]Mike Edwards: Anish proposal:

[11:50]Mike Edwards:

[11:50]anish:

[11:50]Mike Edwards: Mike's alternate wording:

[11:51]anish: Let S be the set of fully qualified names of the interface classes identified by the bean references. s1, s2 S, s1 is either an ancestor or descendant of s2 in the class inheritance tree. If this condition does not hold true then the SCA runtime MUST raise an error [SPRxxxx]. The interface attribute is set to that member of S whose depth in the inheritance tree is the highest amongst all the members of S. I.e., it is set to the most specific subclass amongst all the interface classes identified by the bean references.

[11:56]MartinC: Mike's basic objection is the mathematical phrasing and proposes a more english frienedly wording

[11:57]MartinC: collection is a better word than set

[11:59]anish: Each interface class in the collection of interface classes has to be either the same as, or an ancestor of, or a descendent of, each other interface class in that collection.

[12:00]MartinC: Motion: Mike E moves to resolve 225 with wi=oring in message 21 as modified by anish's text immidately proceeding motion text

[12:00]Bryan Aupperle: Fyi, the mathematical term for what we are discussion is a bag.

[12:01]MartinC: s/wi=oring/wording/

[12:01]MartinC: 2nd bryan

[12:02]MartinC: passed w/o

[12:02]MartinC: AOB

[12:02]MartinC: stragglers: none

[12:02]MartinC: closed

Page 1 of 5