Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Automatic display of object relationships(How to get object relations to render automatically)
Automatic display of object relationships [message #764398] Mon, 12 December 2011 05:00 Go to next message
Roelie viviersFriend
Messages: 2
Registered: December 2011
Junior Member
Hi,

New to Papyrus and have a question creating a component diagram.

I have two component objects with a dependency link between the two components.
When I create a new component diagram and drag the two components to my diagram
it does not automatically render the dependency between the two objects.

Have this be achieved? Is there a setting or maybe I'm using the wrong type of
diagram..

Regards
Roelie
Re: Automatic display of object relationships [message #764566 is a reply to message #764398] Mon, 12 December 2011 12:56 Go to previous messageGo to next message
Timothy Marc is currently offline Timothy MarcFriend
Messages: 547
Registered: July 2009
Senior Member
Hi Roelie,

though I'm interested in the answer itself, my comment won't give you the
correct answer, but another interesting about DirectedRelationship in
Papyrus. If you drag'n'drop a DirectedRelationship onto the canvas all
source and target elements are visualized automatically.

But again, I'm personally curious about the answer to your question.

Timothy

"Roelie viviers" schrieb im Newsbeitrag
news:jc41pp$qmh$1@news.eclipse.org...

Hi,

New to Papyrus and have a question creating a component diagram.

I have two component objects with a dependency link between the two
components.
When I create a new component diagram and drag the two components to my
diagram
it does not automatically render the dependency between the two objects.

Have this be achieved? Is there a setting or maybe I'm using the wrong type
of
diagram..

Regards
Roelie
Re: Automatic display of object relationships [message #764922 is a reply to message #764566] Tue, 13 December 2011 05:21 Go to previous messageGo to next message
Roelie viviersFriend
Messages: 2
Registered: December 2011
Junior Member
Hi Timothy,

Thanks for the feedback. You are correct, dragging the dependency in the diagram brings the supplier+client into diagram also.
Although a nice feature this is not typically what we want when doing architecture design. We want to re-use existing relationships
between systems and dropping two components on the diagram should give us all its dependencies.

The other nice feature that does not seem to be available is that Component 1 gets the dependency registered but not Component 2.
That is component 1 knows it is dependant on component 2 but component 2 does not know component 1 is dependent on it.

Regards
Roelie
Re: Automatic display of object relationships [message #765205 is a reply to message #764922] Tue, 13 December 2011 16:05 Go to previous message
Eclipse UserFriend
Hi Roelie,

>The other nice feature that does not seem to be available is that Component
>1 gets the dependency registered but not Component 2.
>That is component 1 knows it is dependant on component 2 but component 2
>does not know component 1 is dependent on it.

Well, this is given with the native UML::Dependency capability. If Component
1 depends on Component 2 (i.e. Component 1 is the source of the dependency)
than Component 2 participates in the relationship, but does not know
anything about incoming dependencies. Then, you get access to Component2
from Component1 via Component1.classifierDependency.

But if your statement means that Papyrus does not allow to specify those
attributes through the UML section in properties view, you're right. You can
still use those features via the 'Advanced' section in properties view (what
is quite inconvenient). I already filed a bug entry for this. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=366406

Regards,
Marc-Florian

"Roelie viviers" schrieb im Newsbeitrag
news:jc6nd4$1lr$1@news.eclipse.org...

Hi Timothy,

Thanks for the feedback. You are correct, dragging the dependency in the
diagram brings the supplier+client into diagram also.
Although a nice feature this is not typically what we want when doing
architecture design. We want to re-use existing relationships
between systems and dropping two components on the diagram should give us
all its dependencies.

The other nice feature that does not seem to be available is that Component
1 gets the dependency registered but not Component 2.
That is component 1 knows it is dependant on component 2 but component 2
does not know component 1 is dependent on it.

Regards
Roelie
Previous Topic:PapyrusUML install problems in Eclipse Indio
Next Topic:Aggregation in Papyrus
Goto Forum:
  


Current Time: Sun Jan 26 02:32:14 GMT 2020

Powered by FUDForum. Page generated in 0.01942 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top