Next in thread → Next in month →

Re: [sca-c-cpp] NEW ISSUE: C++ componentType file name and location

From
Andrew Borley <>
Date
2007-12-11T10:30:17+00:00
ID
Thread
Re: [sca-c-cpp] NEW ISSUE: C++ componentType file name and location
This issue has been assigned id CCPP-26
in the Jira system. 

See http://www.osoa.org/jira/browse/CCPP-26

Andrew

____________________________________________________________

Andrew Borley

Websphere ESB Development

Tel: 245393 Ext: +44 (0) 1962 815393 Mob: +44 (0) 7971 805547

E-mail: 

Mailpoint 211, IBM (UK) Ltd, Hursley Park, Winchester, Hants, SO21 2JN

____________________________________________________________

Bryan Aupperle <> wrote on
10/12/2007 20:36:51:

> 

> TARGET: C++ C&I Specification 

> 

> Description:  We need to finalize the name and location of 

> componentType files as well as any other SCDL metadata related to

> componentType files. 

> 

> Key points from the assembly specification: 

> - Lines 482-483 of WD01 state that the componentType file has the

> same name as the implementation file but the extension .

> componentType.  But the location is implementation technology

> dependent (lines 484-486). 

> - In the SCDL, the component only defines the componentType 

> indirectly via the implementation.xxx 

> - The componentType schema does not provide a name for a componentType

> 

> As I see the requirements: 

> - The information in implementation.xxx must uniquely identify the

> componentType file. 

> - It needs to be possible to find the file in a simple manner. 

> - It is reasonable to expect multiple component implementations to

> be compiled into a single DLL/shared library/etc. 

> 

> Proposal: 

> Naming:  There are two choices. 

> 1) The implementation name is considered to be the implementation

> header name.  This implies an implementation header MUST only

> contain one class defining a componentType (it MAY contain other classes).

> 2) The implementation name is considered to be the implementation

> class name.  This means if the implementation class is the only

> class in the header file then the header file must be parsed to find

> the class name.  Alternatively we could make the implementation

> class attribute required. 

> 

> I favor option 1 as the least metadata to specify and being 

> consistent with common programming practice. 

> 

> Location: The current text requires a header file that declares the

> implementation class and that this file be available from the SCA

> registry/repository - specifically using a relative path from the

> composite root.  The logical place for the componentType file
to be 

> placed is in the same directory as the implementation header file.
 

> The only reason I can think of to do something different is if we

> believe there is a requirement to place implementation header files

> in a directory with restricted access and componentType files in a

> publically readable directory.  I do not believe this is a requirement.

> 

> 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
Next in thread → Next in month →