OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [sca-assembly] ISSUE 5: Component type allows to specify wire targets on references: PROPOSAL


 
I am guessing that the rationale behind the following proposal to close the Issue 5 with no-action is - to allow for direct deployment of implementation artifacts without requiring creation of any SCDL files, etc. Assuming that as the target use case ....
 
I would like to note that supporting the above use case does not depend upon inclusion of deployment specific configuration (e.g. wire targets on references) in the ComponentType, since a simple solution to meet the use case would be to embed the deployment specific configuration directly in the implementation artifacts. Now an interesting question to answer would be - Is there a language-neutral SCA construct to represent the deployment specific configuration embedded in the implementation artifacts? Here are some of the possible answers IMO -
 
a> None - there is no need to separately represent the embedded configuration data as an SCA construct, since the goal of the use case is to avoid creation of any SCDL files, etc.
b> Composite  - Since the SCA model expects that it is a Composite that gets deployed to an SCA domain, it logical follows that the SCA construct to represent the deployment specific configuration embedded in an implementation artifact would also be a Composite (and not ComponentType)
 
So if at all we wanted to have an SCA construct that reflects the deployment specific configuration in a directly deployable implementation, we should focus on defining a mapping between a Composite and the implementation. Mapping of deployment specific configuration embedded in implementation artifacts to ComponentType is not necessary, and if allowed for whatever reasons, there are potential downsides as documented in the issue text [1].
 
In essence, I propose that we resolve Issue-5 by adopting the proposal specified in the issue text, which says: Change the schema so that wire targets cannot be specified.
 
Thanks,
Sanjay
 
 
[1] http://osoa.org/jira/browse/ASSEMBLY-5


From: Mike Edwards [mailto:mike_edwards@uk.ibm.com]
Sent: Tuesday, Feb 12, 2008 4:12 AM
To: OASIS Assembly
Subject: [sca-assembly] ISSUE 5: Component type allows to specify wire targets on references: PROPOSAL


Folks,

PROPOSAL:  Close Issue 5 with no action.

This permits the component type of a component to contain wire targets on references.


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:  mike_edwards@uk.ibm.com






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








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]