[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw chat log of 2008-11-11 morning session
Mark Combellack: 9:00 to 9:15 Welcome Roll call Appointment of scribe for day 1 Agenda bashing Approval of minutes of 3rd November call http://www.oasis-open.org/committees/download.php/29906/SCA%20Java%20Minutes%202008-11-03.doc 9:15 - 9:30 Accepting new issues None at the moment 9:30 - 10:40 Local Interfaces, pass by reference and multiple services JAVA-56 When more than one interface with the same unqualified name used in the @Service annotation Proposal at http://lists.oasis-open.org/archives/sca-j/200811/msg00006.html JAVA-3 Local services expose implementation classes as their type No proposal but some discussion http://lists.oasis-open.org/archives/sca-j/200808/msg00098.html JAVA-6 @AllowsPassByReference requires more detailed description No proposal some suggestions in Jira 10:40 - 11:00 Break 11:00 - 11:02 2 Minutes silence for Remembrance Day See http://en.wikipedia.org/wiki/Remembrance_Day#United_Kingdom 11:02 - 12:45 Scopes and Package names JAVA-28 Package Name Changes http://lists.oasis-open.org/archives/sca-j/200811/msg00017.html JAVA-21 Clarify Request Scope lifetime Proposal in Jira and http://lists.oasis-open.org/archives/sca-j/200811/msg00005.html Previous discussions at http://lists.oasis-open.org/archives/sca-j/200803/msg00034.html JAVA-30 "Process" Scope Proposal in Jira and at http://lists.oasis-open.org/archives/sca-j/200807/msg00068.html 12:45 - 1:45 Lunch 1:45 - 3:40 Callbacks JAVA-25 Callback Simplification Proposals at http://lists.oasis-open.org/archives/sca-j/200803/msg00063.html and http://lists.oasis-open.org/archives/sca-j/200809/msg00089.html Some discussion at http://lists.oasis-open.org/archives/sca-j/200804/msg00035.html JAVA-67 Need normative rules for stateful callbacks No proposal JAVA-69 Misleading statement about lifetime of stateful callbacks (Pending proposal from Simon) JAVA-19 Redirecting callbacks Proposal in Jira JAVA-73 Incorrect reference to "original request" Proposal in Jira JAVA-52 RequestContext.getCallbackReference() description inadequate Proposal in Jira JAVA-74 Clarify meaning of "should implement" No proposal JAVA-76 Incorrect code in section 6.7.4 examples (Pending proposal from Simon) 3:40 4:00 Break 4:00 - 6:00 Callbacks (continued) 6:00 Adjourn Ashok: test anish: scribe: anish anish: Topic: agenda bashing anish: Jim is interested in callback/conversation, so will delay it by an hour anish: callback/conversation topic will be reordered anish: agenda approved with one change anish: Topic: approval of minutes from 2008-11-03 anish: http://www.oasis-open.org/committees/download.php/29906/SCA%20Java%20Minutes%202008-11-03.doc anish: minutes approved w/o anish: Topic: new issues anish: no new issue anish: s/issue/issues anish: Topic: Issue 56 anish: JAVA-56 When more than one interface with the same unqualified name used in the @Service annotation Proposal at http://lists.oasis-open.org/archives/sca-j/200811/msg00006.html anish: Mark explains the issue anish: ... and the proposal Mark Combellack: If a Java implementation needs to realize two services with the same interface or two services with the different interfaces that have the same simple class name, then this is achieved through subclassing of the interface. Mark Combellack: If a Java Implementation defines a @Service annotation that lists two interfaces with the same simple class name, the SCA Runtime MUST not deploy that Component Mark Combellack: Add words between the *** to the paragraph on line 1687: If a Java implementation needs to realize two services with the same interface *** or two services with different interfaces that have the same simple name, *** then this is achieved through subclassing of the interface. Add the following extra paragraph before line 1690: If a Java Implementation defines a @Service annotation that lists two interfaces with the same simple name, the SCA Runtime MUST not deploy that Component Mark Combellack: Add words between the *** to the paragraph on line 1687: If a Java implementation needs to realize two services with the same interface *** or two services with different interfaces that have the same simple name, *** then this is achieved through subclassing of the interface. Add the following extra paragraph before line 1690: If a Java Implementation defines a @Service annotation that lists two interfaces with the same simple name, the SCA Runtime MUST NOT deploy that Component Mark Combellack: It is not possible for Components to have Services with the same Java simple name. Mark Combellack: It is not possible a Components to have more than one Service with the same Java simple name. Mark Combellack: It is not possible a Component to have more than one Service with the same Java simple name. Mark Combellack: It is not possible for a Component to have more than one Service with the same Java simple name. anish: A Component MUST NOT have two Services with the same Java simple name. Mark Combellack: If a Java implementation needs to realize two services with the same simple name then this can be achieved through subclassing of the interface. anish: A component MUST NOT have two services with the same Java simple name. Mark Combellack: If a Java implementation needs to realize two services with the same Java simple name then this can be achieved through subclassing of the interface. Mark Combellack: Replace paragraph at 1687-1689 with: A component MUST NOT have two services with the same Java simple name. If a Java implementation needs to realize two services with the same Java simple name then this can be achieved through subclassing of the interface. anish: Mark moves Anish Seconds to resolve issue 56 by replacing paragraph at 1687-1689 in CAA CD01 spect with: anish: A component MUST NOT have two services with the same Java simple name. If a Java implementation needs to realize two services with the same Java s anish: imple name then this can be achieved through subclassing of the interface. Dave Booz: ping anish: motion approved w/o anish: Resolution: issue 56 is resolved with the above motion anish: Topic: Issue 3 anish: JAVA-3 Local services expose implementation classes as their type No proposal but some discussion http://lists.oasis-open.org/archives/sca-j/200808/msg00098.html Mark Combellack: More discussions at: http://lists.oasis-open.org/archives/sca-j/200810/msg00039.html anish: Discussion on addition of @Local annotation. anish: @Local can be used in an interface, whereas @service has to be in the impl class Mark Combellack: Breaking until 11:20 Mark Combellack: Resuming anish: Action: SimonN to raise 3 issues for each C&I wrt what happens if the annotation rules are not followed (SCA runtime MUST NOT deploy the component) anish: Simon moves Dave seconds to close issue 3 with no action anish: motion approved w/o anish: Resolution: Issue 3 is closed with no action anish: Topic: Issue 6 anish: JAVA-6 @AllowsPassByReference requires more detailed description No proposal some suggestions in Jira anish: MikeE: two ways: a) get rid of the annotation, OR b) allow the same annotation for the reference (on the client side) anish: Action: MikeE to raise an issue in Assembly regarding @AllowPassByReference anish: Mark: do we have consensus on a direction for this anish: Action: Simon to provide proposal for issue 6 anish: Topic: issue 28 anish: Mary has come back and suggested org.oasisopen but has said that it is not necessary for OASIS to own this anish: General consensus that this does not make sense anish: Anish moves Simon seconds that using org.oasisopen without OASIS acquiring ownership of the domain does not make sense. And if OASIS is not willing to buy this domain we prefer to continue with the org.osoa package name anish: motion approved w/o anish: Action: Dave to draft email to raise an objection to TC admin decision anish: Lunch anish: resume @ 1:30pm
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]