Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 101607 - Association navigability
Summary: Association navigability
Status: RESOLVED DUPLICATE of bug 85179
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 2.0.0   Edit
Assignee: Kenn Hussey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 75922
Blocks:
  Show dependency tree
 
Reported: 2005-06-24 05:19 EDT by Ferenc Kovacs CLA
Modified: 2005-09-27 11:16 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ferenc Kovacs CLA 2005-06-24 05:19:45 EDT 
Right now, the creation of associations is connected to the
org.eclipse.uml2.Type interface (which is subinterfaced in eg.
org.eclipse.uml2.Class). However finding associations, in which a class is
involved is difficult, because the getAssociation method resides in the
org.eclipse.uml2.Property interface. As a consequence, in the case of
not-navigable associations iterating through the attributes of a given class
does not give correct results. Considering that an association can be moved
inside the model wherever you want in worst case you should iterate all of the
associations in a modell to make sure, whether the class is involved in such a
relationship.
Comment 1 Kenn Hussey CLA 2005-06-27 11:15:19 EDT 
A resolution to bug 75922 should reduce the overhead of querying reverse 
references, at which time it may be practical to add methods to obtain, for 
example, the associations in which a type is involved. See also bug 85179 for 
a discussion of convenience methods related to relationships.
Comment 2 Kenn Hussey CLA 2005-09-27 11:16:11 EDT 
This bug will be resolved when (efficient) convenience methods are added for 
retrieving the relationships involving a given element.

*** This bug has been marked as a duplicate of 85179 ***