Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ellidiss-release
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TASTETASTE
  • ellidiss-release
  • Issues
  • #1
Closed
Open
Issue created Nov 28, 2016 by Elena Alana Salazar@ealanaDeveloper

TASTE GUI - Modifications in the input file

Hello,

We are having problems when opening a Deployment View with TASTE GUI.

We created a Deployment View (DeploymentView1_ORIGINAL.aadl attached) and we want to open it with TASTE GUI. However, when the file is opended, TASTE GUI modifies it, for example:

  • It includes Ellidiss copyright
  • Comments are removed
  • It reorganizes and removes (e.g. WITH interfaceview::IV;) some parts.

When we define distributed systems, the problem gets worse. For example, in the DeploymentView2_ORIGINAL.aadl, the following information is removed (please, note that in that case we did not include the TASTE coordinates). CONNECTIONS obj_PBConnectionDockprocessor_board_12 : BUS ACCESS PM_PB2_Bus -> processor_board.processor_board_PBConnectionDock_link; obj_PB2ConnectionDockprocessor_board_2_13 : BUS ACCESS PM_PB2_Bus -> processor_board_2.processor_board_2_PB2ConnectionDock_link; PROPERTIES Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_DataPublishing_Component2_impl_instdataT; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_EventPublishing_Component2_impl_instc2_event; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_DataPublishing_FDIR_impl_instFDIR_DataSet; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_EventPublishing_FDIR_impl_instEvent_FDIR_Error; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_DataPublishing_Component2_impl_inst_redundantdataT; Actual_Connection_Binding => (reference (PM_PB2_Bus)) applies to interfaceview.obj_processor_board_2_EventPublishing_Component2_impl_inst_redundantc2_event; Is there any way to avoid that TASTE GUI modifies the input file? Can we avoid that it removes the connections and properties of distributed systems? In both cases, we are able to generate the executable using TASTE tools.

DeploymentView1_ORIGINAL.aadlDeploymentView1_TASTE_GUI.aadlDeploymentView2_TASTE_GUI.aadlDeploymentView2_ORIGINAL.aadl

Thank you in advance, Elena

Edited Oct 09, 2022 by Maxime Perrotin
Assignee
Assign to
Time tracking