NEW ISSUE: Conflicting domain-level <wire> deployments

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

 

RAISER: Michael Rowley

 

TARGET: SCA Assembly Specification WD 2, section 6.4 Wire

 

DESCRIPTION:

 

If a component is deployed with a wire target, and then a later deployment includes a <wire> for the same component reference, what should happen?

 

Is the answer different if the multiplicity is 0..1, 1..1 or 0..n?  If we treat 0..n so that new <wire> add targets for the reference, is there any way to remove targets?

 

What should happen for later conflicting <wire> deployments?

 

PROPOSAL:

 

(informally) Later wire deployments should override existing wire deployments for 0..1 or 1..1 references.  For 0..n references, new <wire target=””> elements are additive.  We should introduce a new attribute <wire all_targets=””> which replaces the complete list of targets for the @source.