Book a Demo

Author Topic: enum class does not link with a relation?  (Read 14654 times)

Josef Stadelmann

  • EA User
  • **
  • Posts: 59
  • Karma: +0/-0
  • as simple as possible, but not too simple
    • View Profile
enum class does not link with a relation?
« on: April 15, 2015, 05:21:49 pm »
I have two classes
a) an Interface InterProcessComm::IInterProcessConnection and
b) a class NamedPipes::PipeHandle
each of it has an attribute names State which is of type InterProcessComm::InterProcessConnectionState

When I drag-drop and then link the class InterProcessComm:: InterProcessConnectionState to my class that diagram where the other two classes are already there, I would expect that a relation would be drawn automatically as it happens for all other classes. But that is not the case. It just does not happen as it does for all other classes and interfaces.

Is that my misunderstanding, do I have anything I left of, or can it be that I do something wrong, an oversight, OR is this an EA BUG?
Josef
« Last Edit: April 15, 2015, 05:28:39 pm by stadelma »

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: enum class does not link with a relation?
« Reply #1 on: April 15, 2015, 05:34:06 pm »
You mean drag and drop as instance (because of the "and then link")? An instance is independent from its classifier. You can choose to copy the class connections on creation (IIRC as I don't use that) but thta's it.

q.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: enum class does not link with a relation?
« Reply #2 on: April 15, 2015, 07:09:43 pm »
Josef,

Attributes and connectors are treated as separate artifacts by EA.
This means that the "relation" introduced by the attribute state is not represented as a connector (such as an association or dependency)

So you'll have to choose whether to model the relations as attributes or as associations.
I've documented my best practice regarding this issue a while ago: UML Best Practice: Attribute or Association

Geert