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: ISSUE 48: Defaulting composite reference targets to internal components



http://www.osoa.org/jira/browse/ASSEMBLY-48

On Feb 12, 2008, at 6:44 AM, Michael Rowley wrote:

>
> RAISER: Michael Rowley
>
> TARGET: SCA Assembly Specification, section 6.2 in WD02
>
> DESCRIPTION:
>
> It is often desirable for software to offer some ability to  
> customize or replace some capability that is available “out of the  
> box”.
>
> In a composite, the out-of-the-box behavior would be represented by  
> components within a composite.  The ability to customize the  
> composite is represented by composite-level references.  What is  
> missing is the ability to specify that some internal component  
> should be used _unless_ the composite is customized by setting one  
> of its composite references.
>
> PROPOSAL:
>
> Composite references should have a new @internalDefault attribute,  
> which is like the @target attribute, except that it resolves to a  
> service that is within the same composite (recall that the value of  
> the @target attribute is resolved in the context of where the  
> composite is _used_, so internal components of the composite are not  
> visible to it).  At most one of @internalDefault and @target can be  
> set.  As with @target, the value of @internalDefault is used for the  
> reference unless the reference target is explicitly set by the user  
> of the composite (i.e. by the component that uses it via  
> <implementation.composite>).
>
>
>



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