RE: [sca-assembly] ISSUE 6: usage of not promoted references

["Michael Rowley" <mrowley@bea.com>]

I believe that an unpromoted binding must have a URI (or EPR)
designating a target service, or the reference itself must be internally
wired.  If a target service is not provided in any way, then the
programming model should represent the reference as null (or some
equivalent for the language in question).  If the reference has a
multiplicity of 1..1 or 1..n, then such an unresolved reference should
generate a deployment error.

If the binding does designate a target, then if the reference is not
promoted, then neither the target nor the binding can be overridden.  If
the reference is promoted, then either can be overridden.  But in both
cases, the reference is operational.

I agree this could be clarified, probably in the binding section.

Michael

-----Original Message-----
From: Martin Chapman [mailto:martin.chapman@oracle.com] 
Sent: Friday, October 05, 2007 6:40 AM
To: sca-assembly@lists.oasis-open.org
Subject: [sca-assembly] ISSUE 6: usage of not promoted references

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

>-----Original Message-----
>From: Peshev, Peter [mailto:peter.peshev@sap.com] 
>Sent: Friday, October 05, 2007 7:58 AM
>To: sca-assembly@lists.oasis-open.org
>Subject: [sca-assembly] NEW ISSUE: usage of not promoted references
>
>
>TARGET: SCA Assembly Specification
>
>DESCRIPTION: If a component X has a reference with a binding 
>attached to it (ws.binding or jms.binding) and with no target 
>in SCA terms, and that component is used in a composite 
>however the reference is NOT listed as promoted. Is the 
>reference still operational and what should happen if the 
>component code invokes it ?
>
>That describes the common use case when a component is calling 
>non-SCA world and that component needs to be used in an 
>assembly. Does the assembler needs to promote a reference all 
>the way up to the domain or he/she can leave it as it is ?
>
>PROPOSAL: Clarify the issue, and add a separate section in the 
>spec with examples how components calling non-SCA code via 
>standard bindings can be used in assembly.
>
>
>