Null data acess reference in SharedDataAction objects

[Etienne13]

Summary

Although the type checking resolves the data access reference of SharedDataAction objects, their valuation appears to be null at the end of the execution of the BA plugin.

Expected and Current Behavior

After parsing and resolving, a BA subclauses, SharedDataAction objects should either raise an error because the data access cannot be resolved, or the data access should be registered in the SharedDataAction object. Using the following example, there is no resolution error for the data access but it does not appear in the SharedDataAction object.

package test_lock_actions
public
	
	thread th
		features
			d: requires data access dt;
		annex behavior_specification {**
			states
				s1: initial complete final state;
			transitions
				s1 -[on dispatch]-> s1
					{
						computation(1 ms..2ms);
						d!<;
						computation(0 ms..2ms);
						d!>;
						computation(3ms..4ms)
					};
		**};
	end th;

	data dt	
	end dt;
	
end test_lock_actions;

Environment

• OSATE Version: OSATE 2.7.1
• Operating System: Linux, ubuntu

[Etienne13]

Although this issue has been fixed for data accesses in lock actions, it was poorly tested for unlock actions and the issue remained in this case. I therefore reopen this issue and will propose a fix and some improvement of the corresponding test case very soon.