Book a Demo

Author Topic: Adding connectors  (Read 2925 times)

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
Adding connectors
« on: October 01, 2010, 07:25:32 am »
I start a new diagram, add some existing entities to it.
Using the Toolbox I select the associate deployment relationship, then drag with the LMB on from one entity for another.
A dotted line appears to connect the two, then after a second or two disappears, no other message appears.
What gives?
Orthogonality rules
Position and Team disestablished, thanks austerity.
Now itinerant.

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
Re: Adding connectors
« Reply #1 on: October 01, 2010, 07:48:29 am »
OK, so I tried again using the quick link feature I get the error message


I wonder why I couldn't get this message before?

Now heres the question though,
why do they have to be unlocked? (I'm not changing them)
« Last Edit: October 01, 2010, 07:49:20 am by skiwi »
Orthogonality rules
Position and Team disestablished, thanks austerity.
Now itinerant.

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
Re: Adding connectors
« Reply #2 on: October 01, 2010, 07:51:48 am »
And here is another interesting thing, I don't have to unlock both entities to make the association, just one (either source or target) will do?

I'd love to understand this.
« Last Edit: October 01, 2010, 07:52:26 am by skiwi »
Orthogonality rules
Position and Team disestablished, thanks austerity.
Now itinerant.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Adding connectors
« Reply #3 on: October 01, 2010, 03:21:59 pm »
Well, the idea is good, but the implementation sort of failed :-X
When you add a relationship between elements, you are in fact changing them.
Which one you are changing depends on the ownership of the relation.

The problem is that the ownership of a relation isn't always easy to determine (at front)
For things like dependencies and generalizations that is easy. If you are adding such a relationship you are changing the "source" element. (the element on the other side of the arrow).

For asociations that is more complicated. An association can be owned by either the target, source, or none (in this case the package would be the owner). But the issue is that EA can't know who owns the assocation untill you define it in the associations properties.
So the safest would be to only allow new associations when all related elements are locked, and the containing package is locked.

I guess Sparx felt that would be a bit too much, so apparently they decided that at least one of the related elements should be locked for a new Association to be allowed.

Geert