History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: ASSEMBLY-41
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mike Edwards
Reporter: Scott Vorthmann
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OASIS SCA Assembly TC

Conflicting domain-level <wire> deployments

Created: 22/Jan/08 06:55 PM   Updated: 21/Jan/09 04:31 AM
Component/s: Assembly
Affects Version/s: None
Fix Version/s: None


 Description  « Hide

http://lists.oasis-open.org/archives/sca-assembly/200801/msg00049.html


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.
 


 All   Comments   Change History      Sort Order:

Mike Edwards [11/Aug/08 09:21 AM]
Issue subject is extended to cover the topic of updates to Properties at the Domain level, as decided at the Assembly TC meeting of 5th August:

http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/29022/SCA%20Assembly%20minutes%202008-08-05.pdf

Mike Edwards [29/Sep/08 08:00 AM]
Resolved at the Assembly TC meeting of 9th September.

Resolution is as described here:

http://lists.oasis-open.org/archives/sca-assembly/200808/msg00019.html

Mike Edwards [29/Dec/08 05:19 AM]
Applied in this revision:

sca-assembly-1.1-spec-cd01-rev7.doc

23 Dec 2008

Mike Edwards [21/Jan/09 04:31 AM]
CD02