SCA-J Teleconf has been modified by Dr. Michael Rowley
Date: Thursday, 20 December 2007
Time: 01:00pm - 02:00pm ET
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)
Minutes:
This event is one in a list of recurring events.
Other event dates in this series:
Thursday, 27 September 2007, 01:00pm to 02:00pm ET
Thursday, 04 October 2007, 01:00pm to 02:00pm ET
Thursday, 11 October 2007, 01:00pm to 02:00pm ET
Thursday, 18 October 2007, 01:00pm to 02:00pm ET
Thursday, 25 October 2007, 01:00pm to 02:00pm ET
Thursday, 01 November 2007, 01:00pm to 02:00pm ET
Thursday, 08 November 2007, 01:00pm to 02:00pm ET
Thursday, 15 November 2007, 01:00pm to 02:00pm ET
Thursday, 22 November 2007, 01:00pm to 02:00pm ET
Thursday, 29 November 2007, 01:00pm to 02:00pm ET
Thursday, 06 December 2007, 01:00pm to 02:00pm ET
Thursday, 13 December 2007, 01:00pm to 02:00pm ET
Thursday, 03 January 2008, 01:00pm to 02:00pm ET
Thursday, 10 January 2008, 01:00pm to 02:00pm ET
Thursday, 17 January 2008, 01:00pm to 02:00pm ET
Thursday, 24 January 2008, 01:00pm to 02:00pm ET
Thursday, 31 January 2008, 01:00pm to 02:00pm ET
Thursday, 07 February 2008, 01:00pm to 02:00pm ET
Thursday, 14 February 2008, 01:00pm to 02:00pm ET
Thursday, 21 February 2008, 01:00pm to 02:00pm ET
Thursday, 28 February 2008, 01:00pm to 02:00pm ET
Thursday, 06 March 2008, 01:00pm to 02:00pm ET
Thursday, 13 March 2008, 01:00pm to 02:00pm ET
Thursday, 20 March 2008, 01:00pm to 02:00pm ET
Thursday, 27 March 2008, 01:00pm to 02:00pm ET
Thursday, 03 April 2008, 01:00pm to 02:00pm ET
Thursday, 10 April 2008, 01:00pm to 02:00pm ET
Thursday, 17 April 2008, 01:00pm to 02:00pm ET
Thursday, 24 April 2008, 01:00pm to 02:00pm ET
Thursday, 01 May 2008, 01:00pm to 02:00pm ET
Thursday, 08 May 2008, 01:00pm to 02:00pm ET
Thursday, 15 May 2008, 01:00pm to 02:00pm ET
Thursday, 22 May 2008, 01:00pm to 02:00pm ET
Thursday, 29 May 2008, 01:00pm to 02:00pm ET
Thursday, 05 June 2008, 01:00pm to 02:00pm ET
Thursday, 12 June 2008, 01:00pm to 02:00pm ET
Thursday, 19 June 2008, 01:00pm to 02:00pm ET
Thursday, 26 June 2008, 01:00pm to 02:00pm ET
Thursday, 03 July 2008, 01:00pm to 02:00pm ET
Thursday, 10 July 2008, 01:00pm to 02:00pm ET
Thursday, 17 July 2008, 01:00pm to 02:00pm ET
Thursday, 24 July 2008, 01:00pm to 02:00pm ET
Thursday, 31 July 2008, 01:00pm to 02:00pm ET
Thursday, 07 August 2008, 01:00pm to 02:00pm ET
Thursday, 14 August 2008, 01:00pm to 02:00pm ET
Thursday, 21 August 2008, 01:00pm to 02:00pm ET
Thursday, 28 August 2008, 01:00pm to 02:00pm ET
Thursday, 04 September 2008, 01:00pm to 02:00pm ET
View event details:
http://www.oasis-open.org/apps/org/workgroup/sca-j/event.php?event_id=16646
PLEASE NOTE: If the above link does not work for you, your email
application may be breaking the link into two pieces. You may be able to
copy and paste the entire link address into the address field of your web
browser.
