Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to create AADL files/packages #2

Closed
juli1 opened this issue Aug 21, 2011 · 5 comments
Closed

Ability to create AADL files/packages #2

juli1 opened this issue Aug 21, 2011 · 5 comments

Comments

@juli1
Copy link
Contributor

juli1 commented Aug 21, 2011

When I start OSATE2 and start a new AADL project, I am not able to either create an AADL file or even create a new package. Then,if I create the AADL file by myself (using the resources perspective), the AADL perspective
does not recognize the syntax and I cannot generate any AAXL file (unavailable option).

@osate
Copy link
Collaborator

osate commented Aug 25, 2011

The project needs an XText nature: right click on the project, Configure > Add XText nature.
AADL files must have extension .aadl2 in this snapshot. Then the text editor should mark errors, etc.
We forgot to put this in the release notes.
AAXL files are gone for declarative AADL models they only exist for instance models.

@juli1
Copy link
Contributor Author

juli1 commented Aug 25, 2011

Hi,

I tried, it works. However, automatically adding the XText nature would be useful :)
So, now, text is recognized but I'm not able to create aaxl2 files or even instance files. How can I do ?

@lwrage
Copy link
Contributor

lwrage commented Aug 26, 2011

First, right click on the .aadl2 file > Open with... > Aadl2 Editor. That should give you an outline view.
Then, in the outline view, right click on a system implementation. That context menu has actions for instantiation. It also has a save as XMI action, which creates an aaxl2 file. Both actions are also available in the context menu in the aadl text editor.

@juli1
Copy link
Contributor Author

juli1 commented Aug 26, 2011

Indeed, you're right. So, I am able to instantiate the system, no problem at all for that and it creates a .aaxl2 with the instantiated system. However, I don't see the aaxl2 file that correspond to my textual .aadl2 file, is it normal ?

@osate
Copy link
Collaborator

osate commented Aug 31, 2011

Yes, that's normal, we don't need them any more. If you want the aaxl file, use the "Save as XMI" command form the context menu (AADL editor or outline view).

@osate osate closed this as completed Oct 17, 2011
lwrage pushed a commit that referenced this issue May 4, 2018
Added code to skip recover transitions triggered by recover events or by
incoming propagation of type NoError.
This eliminates the recursion problem of issue #2.
AaronGreenhouse pushed a commit that referenced this issue Jun 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants