Hi,

I got a composite class named "Ping", which consists of a subpart named "Pong" (drawn inside the Composite Structure Diagram of Ping).

Both of them have statecharts and a port defined (the ports are connected via a link). All I want to for now is to send events in a particular state of "Ping" via the port to the "Pong" object, which should cause a state transition in the second statechart. (And vice-versa, by sending an event back).

Please see the corresponding diagrams attached below.

Up to now, I was not able to receive the event in the Pong statechart. Can somebody tell me what I'm missing?

P.S.: I've also tried to specify the ports as "Behavior", but that didn't work either

forgot to add that I'm using Rhapsody in C (RiC 7.0)

mmmh that is not working... but pong is a part of ping , so why not adressing its part directly ?

Hi Bob,

I was not used to composite structure diagrams before and therefore was inspired by the last picture on http://de.wikipedia.org/wiki/Konnektor_(UML) - so initially I thought I need ports to be able to communicate with my parts (but when looking precisely at the diagram on that page, it turns out that the part has no port, just a connector).
So if I got it right now, I just need to draw the part inside Ping (with no connector/link at all), and just address the part as usual...

Rgs

Well...Bob, I tried to model it as to your suggestion - my composite structure diagram of Ping now only consists of the nested class Pong - without any ports or links attached to it.

My events are sent now by RiCGEN(&me->itsPong, event_ping()) - instead of sending it to a port as before. This works perfectly well!

However, the other way round it does not work (itsPong is not aware of its parentClass itsPing). Is there a built-in-mechanism to send events/call operations directly on the parent object? Or am I forced to draw some additional association to be able to reference the parent?

I appreciate your help again!

Ah, I found that in the features of the part you can specify whether the parent should be known or not ("knows parent as:").

Ticking this box, my PingPong example works now. Maybe someone can confirm, if this is the correct/intended way of referencing the parent?

thx

yes
per default the relation to the "child" (call it part instead of child) is directional - with the check box bidirectional

well done !

Just throwing it out there, but i believe if you MUST use ports to send to the "whole" for some reason or another, you could also send events to the port in the "whole' by ticking the "behavioral" box.

I was forced to do this once. I had an external class in another subpackage placed as a "part" of another class in another subpackage. For some reason Rhapsody would always throw errors when compiling stating it couldn't find the "whole" object. Does anyone know what might have been causing this?

Thanks