Hi Raymond,
I don't see any other appends on this topic.
In short, the answer is yes, case3 is not valid.
For cases 1 and 2, I presume you forgot to include
@multiplicity. One of the ..n forms would be needed for
both case1 and 2 to be complete.
Dave
----- Original Message -----
From: "Raymond Feng" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, May 25, 2007 2:57 PM
Subject: [SCA Spec] The usage of target attribute and binding URIs for
references
Hi,
The assembly spec allows us to declare targets for a component reference.
Meanwhile, the enclosing binding elements can provide endpoints too. The
following is quoted from the spec.
"Note that a binding element may specify an endpoint which is the target
of that binding. A reference must not mix the use of endpoints specified
via binding elements with target endpoints specified via the target
attribute. If the target attribute is set, then binding elements can only
list one or more binding types that can be used for the wires identified
by the target attribute. All the binding types identified are available
for use on each wire in this case. If endpoints are specified in the
binding elements, each endpoint must use the binding type of the binding
element in which it is defined. In addition, each binding element needs to
specify an endpoint in this case."
To better understand how the effective endpoints are resolved, let's look
at the following cases. (Assuming http://localhost:8080/ is the base URI
for http scheme and sca://domain/local for the sca binding)
Case 1:
<reference name="ref1" target="c1/s1 c2/s2">
<binding.ws/>
<binding.sca/>
</reference>
I think it's valid and it ends up with 4 outbound links for the reference:
http://localhost:8080/c1/s1
http://localhost:8080/c2/s2
sca://domain/local/c1/s1
sca://domain/local/c2/s2
Case 2:
<reference name="ref1">
<binding.ws uri="b1"/>
<binding.sca uri="c1/s1"/>
</reference>
I think it's valid too with 2 outbound links for the reference:
http://localhost:8080/b1
sca://domain/local/c1/s1
Case 3:
<reference name="ref1" target="c1/s1">
<binding.ws uri="b1"/>
</reference>
I think it's invalid because it mixes the usage of "target" and "uri".
Is my interpretation of the spec correct? Am I missing other cases?
Thanks,
Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
