Closed Etienne13 closed 10 years ago
There was an error in the metamodel that made all properties that apply to data implicitly also apply to data access (same for bus and bus access, etc). The problem was that features and components got mixed up which led to problems elsewhere. To make a property applicable to an access feature it must be listed explicitly in the applies to clause. There are probably a couple of places where the standard property sets must be updated.
Fixed.
Dear all,
when testing our RAMSES plugin with the latest version of osate, we face a new issue that appeared a few days ago: the Concurrency_Control_Protocol used to be applicable to data and data access. We use this property to characterise the access protocol of ARINC653 services, applying it to data accesses. In the latest version of OSATE, this property is no longer applicable to data accesses... Which is the source of my new problem.
Maybe I missed that part in the discussions about the modification of AADL, but I need to make sure where this modification comes from: is it a modification of the language, or a modification in the tool only?
Thanks in advance for your answer, Etienne.