Re: [sca-c-cpp] ISSUE 41: Importing/Exporting Header files

Folks,

This makes a lot of sense to me.

SCA Assembly will define the import
/ export of SCA artifacts like Composites and also XML items like WSDL
files.

It seems sensible for the C/C++ TC to
define the import / export of purely C/C++ artifacts such as header files
and executables.

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

Bryan Aupperle <>

06/06/2008 18:28

To



cc

Subject

[sca-c-cpp] ISSUE 41: Importing/Exporting
Header files

We talked about importing and exporting executable files between contributions.
 What do you think about importing and exporting header files (for
interfaces).  This potentially would make it possible to avoid having
to have multiple copies of these files in contributions (i.e. if a component
in contribution A has a reference to a service provided by a component
in contribution B then either both composites have the interface header
or B exports it and A imports it). 

Bryan Aupperle, Ph.D.

STSM, WebSphere Enterprise Platform Software Solution Architect

Master Inventor

Research Triangle Park,  NC 

+1 919-254-7508 (T/L 444-7508)

Internet Address: 

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU