[13:02] Vamsi: Vamsavardhana is Vamsi
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw minutes for 22 May
[13:00] Simon Nash: 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/28356/SCA%20Java%20Minutes%202008-05-15.doc 1. Review action items: (5/22) Vamsi to send update to ISSUE-39 description and proposal for inclusion in the JIRA (5/22) Editors to provide date for when WD03 will be available (5/22) Simon to produce updated proposal for issue 23 2. Accepting new issues: NEW ISSUE: equals() method on ServiceReference and CallableReference RAISER: Mark Combellack http://lists.oasis-open.org/archives/sca-j/200805/msg00039.html Latest email: http://lists.oasis-open.org/archives/sca-j/200805/msg00041.html 3. Open issues discussion: JAVA-28: Package Name Changes http://www.osoa.org/jira/browse/JAVA-28 Latest email: http://lists.oasis-open.org/archives/sca-j/200805/msg00043.html JAVA-23: Asynchronous Client interface to Synchronous Service not well described in Java Common Annotations & APIs Specification http://www.osoa.org/jira/browse/JAVA-23 Latest email: http://lists.oasis-open.org/archives/sca-j/200805/msg00044.html JAVA-25: Callback Simplification http://www.osoa.org/jira/browse/JAVA-25 Proposal from Simon: http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/27733/JAVA-25-Proposal-2.doc Proposal from Michael R and Jim: http://www.oasis-open.org/apps/org/workgroup/sca-j/email/archives/200803/msg00014.html Latest Email: http://lists.oasis-open.org/archives/sca-j/200804/msg00035.html JAVA-1: Accessing SCA Services from non-SCA component code http://www.osoa.org/jira/browse/JAVA-1 Latest email: http://lists.oasis-open.org/archives/sca-j/200804/msg00018.html (PPT link at the bottom) 4. Adjourn --------------------------------------------------------------- Rotating scribe list: Peter Walker Sun Microsystems (1) Roberto Chinnici Sun Microsystems (2) Mike Edwards IBM (2) Ashok Malhotra Oracle Corporation (2) Sanjay Patil SAP AG (2) Pradeep Simha TIBCO Software Inc. (2) Bryan Aupperle IBM (1) Peter Peshev SAP AG (2) Ron Barack SAP AG (3) Mark Combellack Avaya, Inc. (1) Anish Karmarkar Oracle Corporation (3) David Booz IBM (3) Martin Chapman Oracle Corporation (2) Michael Beisiegel IBM (3) Jim Marino Individual (3) ---------------------------------------------------------------
[13:02] Vamsi: Vamsavardhana is Vamsi
[13:03] Bryan Aupperle: Scribe: Bryan Aupperle
[13:04] Bryan Aupperle: Discussion of meeting 5 June added to agenda after Action Items
[13:05] Bryan Aupperle: Minutes of 15 May approved w/o
[13:05] Vamsi: Issue 39 - revised description at http://lists.oasis-open.org/archives/sca-j/200805/msg00036.html
[13:05] Bryan Aupperle: Action Items: Vamsi has sent proposal to list. JIRA has not been updated. Ron to complete.
[13:07] Bryan Aupperle: No comments on this proposal.
[13:08] Bryan Aupperle: Anish - WD03 should be available by next week. (New Action Item)
[13:08] Bryan Aupperle: Issue 23 proposal has been posted and will be discussed later this call.
[13:09] Bryan Aupperle: Dave B. Will call be held on 5 June?
[13:10] Bryan Aupperle: Simon - Likely large overlap and call would be rather late in day in Germany.
[13:11] Bryan Aupperle: Mike R moves to cancel 5 June call, Jim seconds
[13:11] Bryan Aupperle: Motion passes w/o
[13:11] Mark Combellack: link to jira for my new issue is http://www.osoa.org/jira/browse/JAVA-46
[13:11] Ron: JIRA issue 39 has been updated.
[13:12] Bryan Aupperle: New Issues
[13:12] Bryan Aupperle: Issue 46
[13:12] Bryan Aupperle: Mark presents issue
[13:14] Bryan Aupperle: Mark moves to open issue, Mike E. seconds
[13:14] Bryan Aupperle: Issue opened w/o
[13:15] Bryan Aupperle: Open Issues Discussion:
[13:15] Bryan Aupperle: Namespace name:
[13:16] Bryan Aupperle: Simon: Mary has passed request on to IT and awaiting response.
[13:16] Bryan Aupperle: Issue 23:
[13:16] Bryan Aupperle: Latest proposal: http://lists.oasis-open.org/archives/sca-j/200805/msg00044.html
[13:18] Bryan Aupperle: Simon: For changes - conformance targets (SCA runtimes), service side details, some "ands" in "a", "b", "c" sections and clarified contract wording
[13:19] Bryan Aupperle: Mike R. Moves to resolve issue with this proposal, Dave seconds.
[13:19] Bryan Aupperle: Motion passes w/o - Issue 23 is resolved.
[13:19] Bryan Aupperle: Issue 25:
[13:19] Bryan Aupperle: Latest comments: http://lists.oasis-open.org/archives/sca-j/200804/msg00035.html
[13:21] Bryan Aupperle: Mike R: We should start by walking through my code example of 10 April (scroll down in latest email)
[13:22] Bryan Aupperle: Mike R walks through this example
[13:27] anish can someone remind what the a, b, c cases where?
[13:28] Dave Booz: a=pure client, b=conversational scoped service, c=backend provider
[13:28] Bryan Aupperle: Mike R: points out that the client in the example is a "B"
[13:34] Bryan Aupperle: Mark: In the stateless case is there a problem if the client is being used on multiple threads concurrently?
[13:34] Bryan Aupperle: Mike R: since this is stateless, that would be very difficult to arrange
[13:35] Bryan Aupperle: Mike E: observes that the same kind of structure shown in the stateless case could be used in the conversational case
[13:36] Bryan Aupperle: Mike R: yes, and this could be used to identify which outbound request a reply is for.
[13:37] Bryan Aupperle: Simon: There is a timing window wrt the reply is received before the buy method has progressed to the next statement.
[13:38] Mike Edwards: Fixed if the client get/sets the callback ID before making the operation
[13:38] Bryan Aupperle: Mike R. agrees this is a problem and should get the callback id prior to the outbound request.
[13:39] Bryan Aupperle: Simon: This eliminates the advantage of not having to generate ID
[13:39] Bryan Aupperle: Mike R: I thought we had already agreed that generated IDs would be valid well before a outbound call is made.
[13:40] Bryan Aupperle: Simon: true so reordering is sufficient
[13:41] Bryan Aupperle: Anish: There are cases when the callback ID could not be know prior to outbound call. For example if using WS message IDs.
[13:42] Bryan Aupperle: Simon: But infrastructure would have to provide the callback ID and manage mapping to message ID
[13:45] Bryan Aupperle: Simon: This would require close coordination between the Java SCA infrastructure and the binding implementation.
[13:46] Bryan Aupperle: Mike R: SCA runtime generated ID passed to binding and used a header on outbound call and reply
[13:47] Bryan Aupperle: Anish: Binding is going to act in a more generic manner and not use this header
[13:48] Bryan Aupperle: Mike E: Java layers asks binding for ID when client requests ID.
[13:49] Bryan Aupperle: Mike R: Java layer could generate ID and pass it to the binding.
[13:49] Bryan Aupperle: Mike R: Do we agree this scenario is important to support?
[13:49] Bryan Aupperle: Simon: Given your view of the world, you are correct?
[13:50] Bryan Aupperle: Dave: There are other views with more complicated IDs.
[13:50] Bryan Aupperle: Mike E: ID is simply a tag out outbound message and return message(s).
[13:51] Bryan Aupperle: Dave: Cases where ID is part of business data.
[13:52] Bryan Aupperle: Mike R; My objective is handle common case and other cases can be handled with more involved custom APIs.
[13:53] Bryan Aupperle: Simon: Alternative that is much simpler in stateless case and very nearly as simple in the conversational case: Add a business data-level state object.
[13:54] Bryan Aupperle: Simon: In my example only change is the addition of the order parameter on the confirm request.
[13:56] Bryan Aupperle: Mike R: My impression is that this is like what has to be done in BPEL to point to what in state object represents unique identifier to allow infrastructure to route reply to proper instance.
[13:57] Bryan Aupperle: Simon: The word version of my proposal shows how this handled without needing to looking into state object.
[13:58] Bryan Aupperle: Anish: As far as what flows on the wire, this looks a lot like conversations.
[13:59] Bryan Aupperle: Simon: I agree.
[14:01] Bryan Aupperle: Time expires - Will continue next week as first agenda item.
[14:01] Bryan Aupperle: Role:
[14:01] Bryan Aupperle: Mark Combellack Avaya, Inc. Group Member Bryan Aupperle IBM Group Member David Booz IBM Group Member Vamsavardhana Chillakuru IBM Group Member Mike Edwards IBM Group Member Simon Nash IBM Group Member Jim Marino Individual Group Member Michael Rowley Individual Group Member Martin Chapman Oracle Corporation Group Member Anish Karmarkar Oracle Corporation Group Member Ron Barack SAP AG* Group Member
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]