vatmi / caex-workbench Goto Github PK

Now the architecture allows only accessing the example files with EOL or EVL , as in the instance no code generation is possible.

When using URI "http://www.dke.de/CAEX/300, ecore search for the metamodel in the webpage and is not able to find the model.

Temporary: Changed all dependencies to the core ecore models in CAEX 2.15 and CAEX 3.0 respectively

The component based architecture assumes that each component comes with a skill and corresponding implementation in the form of a stad xml(fbt) file. Whenever the interface "fbtInterface" is found search the path and save the file in the workspace of the IDE in the corresponding folder of the project

What are the entry points of AML file inside 4diac FBs?? is it direclty the header or something else inside the fbt file?

Eventhough EVL is for validation, you can call Java classes from EVL as well. And the second thing good with EVL is that you can write this Guard conditions, which simplifies your effort of looping.

When created Role classes, Interface class etc in different namespaces and refer to this namespaces from the instance hierarchy, And then if we validate the instance hierarchy files with EVL, the inherited aspects from different namespaces are not aavailbale for validation.

Eg: evaluation of return self.roleRequirements.roleClass.name->exists(r | r = 'Product'); for making sure the internal element of type product type can have only the same child yields error; property name not found in Object. This issue resolved by defining the roleclass in the same namespace as the PPU/instance hierarchy file

For sequence it will require to create a template of the sequence inside EGF and then connect different FBs corresponding to individual skills and corresponding precedence will have to be defined,

The evl plugin/AML rules evl files has to be binded with the UI

When used a supported role class/role class requirement, the member elements of the role class such as external interfaces, cannot be inherited by an internal element or SUC which is using this supported role class or role requirement

The workbench cannot read AML files(.aml) files or when renamed to .caex.

Reason the semantics are not syncronised with AML editor generated cases. Fir example, it is named as roleClass in CAEX workbench but RoleClass in AML editor