Raw Text for TC call of 22 February

Roll Call

http://www.oasis-open.org/committees/membership.php?wg_abbrev=sca-j

- Appointment of scribe. List attached
below

- Agenda bashing

- Approval of minutes for 15th February
2010

http://www.oasis-open.org/committees/download.php/36462/SCA%20Java%20Minutes%202010-02-15.doc

0. Administration

- Open Issue Status:

   CAA + POJO:    0

   EJB Binding:   0

   Spring:      
 2

   JEE:      
    6

   Total Open:    8

1. Review action items:

Action Items that I believe are done:

2010-02-15-01: Mike to clean up the
docs, generate the diff

2010-02-15-02: Anish to generate the
PDF and html files

Action Items that I believe are still
to be done:

2009-07-06-01: Dave B to raise to liaison
(so that other C&Is can consider and possibly assembly) that non-XML
based C&Is should state how the conversion of property values happens

2009-07-17-01: Mike to create an example
of the componentType introspection (JAVA-58 )

2009-09-28-05: Dave to look at unstated
prereqs for JCI-TA-8005/8006

2009-11-09-01: Anish to point out specific
locations for editorial corrections (s/./,/) for issue 150 proposal.

2010-02-01-03: Anish to provide non-normative
text to resolve 166 per directional motion

2010-02-01-04: Mike to look at JAVA-182
and prepare a CD draft for Spring C&I

2010-02-15-04: Chairs to submit the
specs to TC admin for PR (when the packages are ready)

2. Progress to Public Review

a. Publishing Code Artifacts (Dave)

Discussion at: http://lists.oasis-open.org/archives/sca-j/201002/msg00056.html

b. Status of POJO (C&I) CD03, CAA
CD04 and EJB Binding CD02

3. Other issues

a. Assembly-218:  Review Interface
Compatibility logic to accomodate @Remotable attribute in the SCDL (Dave)

Latest discussion: http://lists.oasis-open.org/archives/sca-j/201002/msg00044.html

4. New Issues (Requires 2/3rds)

None

5. Remaining Open Issues for JAA and
POJO specifications

None

6. Open Issues with proposals ready
for discussion (Spring/EJB/JEE)

None

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

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

http://www.osoa.org/jira/browse/JAVA-109

Proposal in Jira

Waiting for updated proposal (Vamsi)

b. JAVA-182: SCA Spring C & I specs
needs to refactor text under abstract and introduction

http://www.osoa.org/jira/browse/JAVA-182

No proposal (Ram)

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

http://www.osoa.org/jira/browse/JAVA-174

d. 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

http://www.osoa.org/jira/browse/JAVA-91

Waiting for updated proposal (Mike)

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

http://www.osoa.org/jira/browse/JAVA-93

Waiting for updated proposal (Anish)

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

http://www.osoa.org/jira/browse/JAVA-108

Waiting for updated proposal

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

http://www.osoa.org/jira/browse/JAVA-88

No proposal

Plamen to check whether on his informal
JEE issues list

h. JAVA-166: Spring C&I does not
say anything about SCA annotations

http://www.osoa.org/jira/browse/JAVA-166

Directional proposal: http://lists.oasis-open.org/archives/sca-j/201002/msg00000.html
(Anish)

(Note: May be able to make progress
on JAVA-144 depending on what happens with this issue)

8. AOB

a. Straggler roll call

---------------------------------------------------------------

Rotating scribe list:

Graham Charters IBM (5)

Yang Lei IBM (11)

Plamen Pavlov SAP AG (3)

Mike Edwards IBM (16)

Martin Chapman Oracle Corporation (16)

Bryan Aupperle IBM (21)

Ashok Malhotra Oracle Corporation (18
)

Anish Karmarkar Oracle Corporation (15)

Scribe: Mike Edwards

Agenda:

Add Anish's proposal for Issue 166 as
Item 6a

Minutes from meeting of February 15th:

Accepted without change

Item 1 Action Items

Action Items done:

2010-02-15-01: Mike to clean up the
docs, generate the diff

2010-02-15-02: Anish to generate the
PDF and html files

2010-02-01-03: Anish to provide non-normative
text to resolve 166 per directional motion

Action Items outstanding:

2009-07-06-01: Dave B to raise to liaison
(so that other C&Is can consider and possibly assembly) that non-XML
based C&Is should state how the conversion of property values happens

2009-07-17-01: Mike to create an example
of the componentType introspection (JAVA-58 )

2009-09-28-05: Dave to look at unstated
prereqs for JCI-TA-8005/8006

2009-11-09-01: Anish to point out specific
locations for editorial corrections (s/./,/) for issue 150 proposal.

2010-02-01-04: Mike to look at JAVA-182
and prepare a CD draft for Spring C&I

2010-02-15-04: Chairs to submit the
specs to TC admin for PR (when the packages are ready)

Item 2. Progress to Public Review

a. Publishing Code Artifacts (Dave)

Discussion at: http://lists.oasis-open.org/archives/sca-j/201002/msg00056.html

Dave describes the need to publish code
artifacts - Binary, Source

Anish: I agree with the 4 items

Anish: We should go to Mary with a proposal
that is specific about HOW we want the artifacts published

Dave: I agree with you on that

anish: proposal -- change the front
page matter to include the URIs

anish: ... this means changing the template

Bryan: C++ TC experiences - we may have
to put pointers in the documents that indicate the existence of the code
artifacts

this would require modification of the
specs

Mike: Assembly spec has experience of
some of this - with the test artifacts see here:

http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-testcases-cd01.pdf

test artifacts link takes you here:

http://docs.oasis-open.org/opencsa/sca-assembly/test-sca-oasisopen-org-namespace.html

Link from RDDL file to ZIP:

http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-testcases-cd01.zip

...this gives you all the precedents
that you need

Anish: I'm not sure that putting the
link to artifacts should be under "Related Work" as in the Assembly
Test Suite document

Anish: We should just add a new section
in the frontmatter template - this is something new for OASIS

Anish: Call it something like "Java
APIs" and put it under "Declared XML Namespaces"

Anish: in the frontmatter

Individual test artifacts are here:

http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-testcases-cd01/

anish: how about a new subheading: "Java
Artifact(s) Location"

Bryan: There is a statement in the Conformance
section which indicates that code artifacts take precedence

- this could be a place for a hyperlink

Bryan: Advantage of putting the link
in the frontmatter is that it can be updated without having to vote a new
version of the CD

Ashok: I'd like to point out that W3C
specs often have stuff right on the front page that links to specific artifacts

Martin: If we don't like the template,
that would need to be a request/comment to Mary

Mike moves to publish the following
artifacts on the OASIS site as part of the CD publication and Public Review:

a) ZIP file containing the source APIs
and Annotations

b) JAR file containing the binary APIs
and Annotations

c) ZIP file containing the API and Annotations
Javadoc

d) Expanded (directly viewable form)
of the API and Annotations Javadocs

and the inclusion of URIs to these 4
items in the frontmatter of the specification documents

Anish seconds

Motion passes unanimously

Dave: Javadoc itself needs work to bring
it up to level

Mike: I also think its incomplete at
the moment

ACTION 20100222-01: (Dave & Mike)
Work to get the Javadoc complete and matching the spec for detail

anish: we'll have to be careful about
this, the external files supersede. Maintenance problem -- easy to change
the spec and forget to change the code artifacts

Dave: Sort out the Java CAA first -
once that is done and submitted, then submit the other 2

Item 3. Other issues

a. Assembly-218:  Review Interface
Compatibility logic to accomodate @Remotable attribute in the SCDL (Dave)

Latest discussion: http://lists.oasis-open.org/archives/sca-j/201002/msg00044.html

Mark: This one falls right on the boundary
between Assembly and SCA-J TCs

so we should really discuss it

Dave: The interesting case is where
you have an implementation that when introspected does not have "Remotable"
for a given Service or Reference

Dave: I think this is really at the
feet of the SCA-J TC to sort out

Anish: This is like Assembly "reaching
in and changing the component type"

- or perhaps this is more like the implementation
having a default that the Assembly configuration can override

Dave: Well, this is certainly a "trip
hazard" and that the Java TC needs to deal with it somewhere

Dave: I'm suggesting that we change
a part of the spec that deals with the remotability of an interface

anish didn't know the phrase 'trip hazard'
had to look it up. My initial thought was -- something to do with an acid
trip 

Bryan: At what time is the "effective
component type" computed - and how is this influenced?

Mark: So potentially there is an issue
here that this TC should consider

Mike: So can I take it that Assembly
TC can close its issue and the Java TC will aim to resolve this?

Mark: Yes, something along those lines.

ACTION 20100222-02: Dave will raise
the necessary issue for @Remotable annotation on <interface.java/>

Mark Combellack: 6. Open Issues with
proposals ready for discussion (Spring/EJB/JEE)

a. JAVA-166: Spring C&I does not
say anything about SCA annotations

http://www.osoa.org/jira/browse/JAVA-166

Proposed wording: http://lists.oasis-open.org/archives/sca-j/201002/msg00060.html
(Anish)

anish: "It is not necessary for
an implementation of this specification to

support annotations specified in SCA
Common Annotations and API

Specification [ref]. Such an implementation
can ignore SCA annotations

that are present in classes used by
the application context."

Anish describes the wording

Mark Combellack lowered your hand

Mike: I have a concern that this wording
might imply that there is some standard interpretation of SCA annotations
in a Spring context

Anish: That isn't what was intended

Bryan Aupperle: It is beyond the scope
of this specification to define the interpretation of the annotations specified
in the SCA Common Annotations and API Specification [ref].

Dave: I take this as meaning "you're
on your own...."

COB

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU