Skip to content

Instantiated AADL model doesn't have properties for connections nor features #237

@jeancharles-roger

Description

@jeancharles-roger

Hi (again 😅),

When instantiating the AADL model dataflow.txt/aadl some elements don't keep assigned properties in the result. Neither of connections nor features have the assigned properties from the root system.

Running spar instance --root dataflow_pkg::dataflow.others --format json dataflow.aadl on dataflow.txt/aadl provides: dataflow-instance.json

In the result the connection my_process.c2 doesn't have the property stood::link_position => "350 266 430 266 430 366 480 366" applies to my_process.c2:

{
    ...
    {
      "name": "my_process",
      "category": "process",
      ...
      "connections": [
        {
          "name": "c2",
          "kind": "Port",
          "is_bidirectional": false,
          "source": "t1.output",
          "destination": "t2.input"
        },
        ...

The same is true for the feature my_process.t1.input it doesn't hold any property.

Is it a current limitation or just forgotten ?

Kind regards.
ps: I have also seen that my_process.c1 doesn't appear in the instance result. It is a passthrough so it has a different status but I feel it could be represented.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions