Latest PROPOSAL :
The following description should be added in section 1.6.2 References,
after line 1387 (that line is after the paragraph that explains
attaching a binding to a reference and before the paragraph explaining
callback) :
Promotion of references accessing endpoints via bindings is suggested
practice since it allows the assembler to change the targets of the
references or the specified bindings and encourages component reuse,
however the lack of such promotion by itself MUST NOT cause errors
during deployment or runtime if the target of the reference can be
identified. The assembler is expected to guarantee for an unpromoted
reference with multiplicity 1..1 or 1..n that one of the following
conditions holds : there is either internal wire within the scope of the
current composite or a binding that identifies correctly either the
component/service for a wire to an endpoint within the SCA domain or
the accessible address of some endpoint outside the SCA domain. If the
assembler does not provide these conditions for an unpromoted reference
that has a multiplicity of 1..1 or 1..n, then such an unresolved
reference MUST generate an error at latest during the first attempt to
use the component. If the assembler does not provide these conditions
for an unpromoted reference that has a multiplicity with 0..1 or 0..n ,
then the programming model MUST not generate deployment errors and the
reference's wiring state will be represented in accordance to the
implementation type in question (e.g. null, handle that throws
exceptions when accessed, extensibility hooks, etc.).
For example the following definition MUST NOT generate any error if the
composite is deployed to the domain :
<composite xmlns="
http://www.osoa.org/xmlns/sca/1.0"
name="MyValueComposite">
<component name="MyValueServiceComponent">
<implementation.java class="services.myvalue.MyValueServiceImpl"/>
<reference name="StockQuoteService">
<binding.ws uri="
http://www.sqs.com/StockQuoteService"/>
</reference>
<reference name="StockQuoteService2">
<binding.jms>
<destination name="StockQuoteServiceQueue"/>
<connectionFactory name="StockQuoteServiceQCF"/>
</binding.jms>
</reference>
</component>
<!-- no references and promotion on purpose -->
</composite>
however the following definitions MUST generate error if the reference
defined in the component type has multiplicity 1..1:
<composite xmlns="
http://www.osoa.org/xmlns/sca/1.0"
name="MyValueComposite">
<component name="MyValueServiceComponent">
<implementation.java class="services.myvalue.MyValueServiceImpl"/>
<reference name="StockQuoteService">
<binding.ws uri="
http://www.sqs.com/StockQuoteService"/>
</reference>
<reference name="UnwiredReference">
<!-- the target cannot be determined, that should be an
error-->
<binding.ws/>
</reference>
</component>
<!-- no references and promotion on purpose -->
</composite>