 SCA C and C++ Telecon (Conference Call) |
|
| Name | SCA C and C++ Telecon (Conference Call) |
| Time | Thursday, 17 January 2008, 11:00am to 12:00pm EST
(Thursday, 17 January 2008, 04:00pm to 05:00pm UTC) |
| Description | Chat Room http://webconf.soaphub.org/conf/room/sca-c-cpp-TC Web Conference http://oasis.acrobat.com/ccpptc1701/ |
| Minutes | 0. Role Bryan Aupperle Andrew Borley David Haney Pete Robbins 1. Agenda bashing 2. Accept minutes from SCA-C-C++ TC meeting of 10 January Minutes approved 3. Action Items a. AI-2 (Pete): C++ header files 4. New Issues None 5. Issue Discussion a. http://www.osoa.org/jira/browse/CCPP-21 C++ migration Proposal here: http://lists.oasis-open.org/archives/sca-c-cpp/200801/msg00009.html Approved as modified: change deprecated to removed (two instances) b. http://www.osoa.org/jira/browse/CCPP-27 C componentType files Proposal here: http://lists.oasis-open.org/archives/sca-c-cpp/200801/msg00011.html Approved as modified: 1) Strike last two sentences of first paragraph. 2) .componentType is not included in SCDL and automatically appended by the SCA runtime in locating the file. Instructions to editors to make a similar about automatic append of .componentType in the C++ spec. c. Status of other open issues No progress yet. 6. Conformance Statements: - Are the current conformance statements appropriate? - Are the current conformance statements worded properly? - Are additional conformance statements needed? Start with Section 6.2.4 of the current C++ WD (http://www.oasis-open.org/committees/download.php/25974/sca-cppcni-1.1-spec-wd-02.doc) Discussion of callback scenarios. 3 identified 1)Client instance receives the callback messages Default case, no specific code needed. 2) Another instance of the client component receives the callback messages 3) An instance of another component receives the callback messages (could be a specific instance or a new instance depending on the scope of the component) 2) and 3) are both handled by a getService(), setCallback() sequence. The runtime stores the service address for proper processing. In all cases setCallback takes a service instance address as a arguement. The text needs to be updated to reflect this. 7. AOB |
| Agenda | 0. Role 1. Agenda bashing 2. Accept minutes from SCA-C-C++ TC meeting of 10 January 3. Action Items a. AI-2 (Pete): C++ header files 4. New Issues None 5. Issue Discussion a. http://www.osoa.org/jira/browse/CCPP-21 C++ migration Proposal here: http://lists.oasis-open.org/archives/sca-c-cpp/200801/msg00009.html b. http://www.osoa.org/jira/browse/CCPP-27 C componentType files Proposal here: http://lists.oasis-open.org/archives/sca-c-cpp/200801/msg00011.html c. Status of other open issues 6. Conformance Statements: - Are the current conformance statements appropriate? - Are the current conformance statements worded properly? - Are additional conformance statements needed? Start with Section 6.2.4 of the current C++ WD (http://www.oasis-open.org/committees/download.php/25974/sca-cppcni-1.1-spec-wd-02.doc) 7. AOB |
| Submitter | Dr. Bryan Aupperle |
| Group | OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC |
| Access | This event is visible to OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC and shared with
|