FUML — 8.6.4.2.1 [5]AcceptEventActionActivation::accept(in signalInstance:SignalInstance)

Specification: Semantics of a Foundation Subset for Executable UML Models, FTF – Beta 1 (ptc/08-11-03)
Section: 8.6.4.2.1 AcceptEventActionActivation

Summary:

The AcceptEventActionActivation::accept() unconditionally places values on output pins even if the action does not have any output pin.

Proposed resolution:

Change the operation from:

// Accept a signal occurance for the given signal instance.

// If the action does not unmarshall, then place the signal instance on

// the result pin.

// If the action does unmarshall, then get the feature values of the

// signal instance, and place the values for each feature on the

// corresponding output pin.

// Concurrently fire all output pins while offering a single control

// token.

// If there are no incoming edges, then re-register this accept event

// action execution with the context object.

AcceptEventAction action = (AcceptEventAction) (this.node);

OutputPinList resultPins = action.result;

Debug.println("[accept] action = " + action.name + ", signalinstance = " + signalInstance);

if (this.running) {

if (!action.isUnmarshall)

else {

FeatureValueList featureValues = signalInstance.getFeatureValues();

for (int i = 0; i < featureValues.size(); i++)

}

this.sendOffers();

this.waiting = false;

Debug.println("[fire] Checking if " + this.node.name + " should fire again...");

// if (this.isReady())

this.receiveOffer();

}

}

If isUnmarshall is true, then the action is required to have output pins corresponding to any signal attributes, and the specification is already correct in this case. It is only in the case that isUnmarshall is false that the specification is incorrect in assuming that there must be an output pin.