Book a Demo

Author Topic: Ports owned by too many  (Read 4177 times)

DanG83616

  • EA User
  • **
  • Posts: 180
  • Karma: +0/-0
    • View Profile
Ports owned by too many
« on: June 24, 2008, 04:38:58 am »
I have a composite that contains instances of components. The ports of those subcomponents show in the hierarchy as being owned by both the subcomponent and the composite (component containing the instance of the subcomponent). That seems incorrect to me. I am not sure of the consequences of this behavior yet.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8098
  • Karma: +118/-20
    • View Profile
Re: Ports owned by too many
« Reply #1 on: June 24, 2008, 08:36:55 am »
I'm afraid that I'm not sure exactly what you're seeing.

I'm seeing what I expect.  If I select the port on the instance I get

Port1
  - owned by
    - : Component1 (the instance)
      - owned by
        - Component2


Then if I select the port on the classifier I get

Port1
  - owned by
    - Component1


But the are different elements, even if they are (more or less) representing the same thing.
« Last Edit: June 24, 2008, 08:37:37 am by simonm »

DanG83616

  • EA User
  • **
  • Posts: 180
  • Karma: +0/-0
    • View Profile
Re: Ports owned by too many
« Reply #2 on: June 25, 2008, 03:51:11 am »
First the hierarchy for the subcomponent instance:

Subcomponent
 - owned by
   - Component (the classifier not the instance)

Now the hierarchy of Subcomponent's port:
Port
 - owned by
   - : Subcomponent
   - Component

I didn't expect the Component. I might have reasoned that both instance and classifier of Subcomponent would be listed. Again, not sure of the consequences, positive or negative. Just wanting to understand.

Thanks,
Dan

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8098
  • Karma: +118/-20
    • View Profile
Re: Ports owned by too many
« Reply #3 on: June 25, 2008, 08:10:06 am »
I see what you're talking about.  I believe it's wrong.

Could you please send in a bug report about it?