Raw Notes from SCA-J concall on December 20th 2007

Michael Rowley: Event Description:
US & Canada Toll Free: (866) 484-4232
International Dial-In Number: (702) 894-2358 ACCESS CODE:  960335

Chat room:
http://webconf.soaphub.org/conf/room/sca-j-TC

Agenda:
- 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 from previous meeting(s) http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/26649/raw%20text%20of%20chatroom.doc

2. Accepting new issues:

None submitted.

3 . Issues discussion

Issue #4: Dependency Reinjection

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

There are two outstanding sub-issues:
A) does a reference represent the wire or the wire target (i.e. does it get invalid if the target changes, or is it a "smart" proxy)?
B) does the component context reflect wiring changes during the life time of the component scope?



Regarding the (A) Ron, Peter, and Henning came up with the following proposed assertions: 

1. Services have an address: Service Component Services have an SCA URI, otherwise bindings provide a URI or some equivalent addressing data.
2. Service reference instances are a client view to a service address: It consists of the service address and (if available) a conversation handle (e.g. an ID, a proxy) and interface information.
3. The address and interface association does not change over the life time of a service reference. An exchange (re-deployment) of the addressed service's implementation SHOULD not invalidate a Service reference instance. Technical constraints may however lead to a de-facto invalidation of service reference instances (e.g. cannot consume previously handed out data).

Or, in one paragraph: 

Services have an address, which can be an SCA URI in the case of a service component service or some other addressing data provided by a binding declaration. A service reference instance is a client view to a service address. It consists of the service address and (if available) a conversation handle (e.g. an ID, a proxy) and interface information. The address and interface association does not change over the life time of a service reference instance. An exchange (re-deployment) of the addressed service's implementation SHOULD not invalidate a Service reference instance. Technical constraints may however lead to a de-facto invalidation of service reference instances (e.g. cannot consume previously handed out data).

4. Adjourn

---------------------------------------------------------------
Rotating scribe list:

Martin Chapman Oracle Corporation
Jeff Mischkinsky Oracle Corporation
Peter Peshev SAP AG
Roberto Chinnici Sun Microsystems
Peter Walker Sun Microsystems
Sriram Narasimhan TIBCO Software Inc.
Pradeep Simha TIBCO Software Inc.
Scott Vorthmann TIBCO Software Inc.
Bryan Aupperle IBM
Michael Keith Oracle Corporation
Uday Joshi Oracle Corporation
---- scribed once -----
Anish Karmarkar Oracle Corporation
Mike Edwards IBM
Michael Beisiegel IBM
Ashok Malhotra Oracle Corporation
David Booz IBM
Simon Nash IBM
Jim Marino BEA Systems, Inc.
Sanjay Patil SAP AG
Jason Kinner Oracle
Ron Barack SAP AG (2nd time)