In BA plugin, port dequeue actions are not resolved properly

[Etienne13]

Summary

Port dequeue actions are not resolved properly by the BA plugin, resulting in the creation of port send actions rather than port dequeue actions.

Expected and Current Behavior

After parsing a port dequeue action, the BA metamodel is actually initialized with port send action.

Steps to Reproduce

1. parse the following example
2. unparse the BA subclause

we notice that the port dequeue actions (noted with '?') have been replaced by port send actions (identified by '!').

package test_ba_ports_actions
public
	
	with Base_Types;

    thread t
		features
			ed_in: in event data port Base_Types::Integer;
		annex behavior_specification {**
                  variables
                    v1 : Base_Types::Integer;
                  states
                    s1 : initial complete state;
                    s2 : final state;
                  transitions
                    s1 -[on dispatch]-> s1 {
                      ed_in ? (v1);
                      ed_in ?
                    };
        **};
	end t;
		
end test_ba_port_actions;

Environment

• OSATE Version: 2.9
• Operating System: Linux ubuntu 18.04