Book a Demo

Author Topic: Exposed functionality from interfaces at ports  (Read 12723 times)

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Exposed functionality from interfaces at ports
« on: April 30, 2013, 11:45:59 pm »
I have a rather strange issue. Or simply my memory is deceiving me. I tried this with v10 and 9.3: I have an interface (say IF) which provides some methods. And a class CLS with a port which itself contains a provided interface (say PIF). PIF is not only classified but has a Realize relation to IF. Now when I put CLS onto a sequence diagram and send a message to it, the drop down does not show the methods available from IF. Only if I show PIF within its port attached to CLS it is possible to utilize the methods from IF. But that rather clutters the sequence diagram. I'm pretty sure that I've seen the IF methods even at the CLS instance in a former EA version. Seemed logically to me as the CLS should have all the methods available it provides through its various exposed interfaces.

Another peculiarity which hit me here: it is not enough to classify PIF with IF in the Exposed Interface dialog. You must draw a Realization from PIF to IF in order to see IF's methods at PIF. So why create the classification if it does not provide the methods? Just for the name?

I'll try that with a former EA version (if I find the download link). However, it would be nice to know what's happening here.

q.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Exposed functionality from interfaces at ports
« Reply #1 on: May 01, 2013, 02:04:04 am »
I tried several previous EA versions until I found what I really did: I used a port which realized an interface - without exposed interface. Doing it this way the class inherits the methods realized by the port.

So another question arises: why does a class inherit from its port but ports do not inherit from their exposed interfaces?

q.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Exposed functionality from interfaces at ports
« Reply #2 on: May 07, 2013, 07:11:40 am »
Quote
I tried several previous EA versions until I found what I really did: I used a port which realized an interface - without exposed interface. Doing it this way the class inherits the methods realized by the port.

So another question arises: [highlight]why does a class inherit from its port but ports do not inherit from their exposed interfaces?[/highlight]

q.
Nothing to say?

q.