Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Importing of 0.7.x models - exception when opening CSDs

Hi,

Some comments line below.

/Peter Cigéhn

On 25 May 2016 at 18:18, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
One more thing… I realized that Neon builds are also using 0.7.2 as a version number (we really should have gone to 0.7.[3..9] or 0.8 when we moved to the Neon stream…).

My models were created with the _Mars_ 0.7.* versions.

​To clarify: I did test with the released 0.7.2 version, based on Mars.

​Personally I never refer to the latest build on the Neon track as "0.7.2" (even if it still happen to have that version number), since we already have released 0.7.2.
 

/Charles

On 2016.05.25, at 12:01 , charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:

I tested more of my models and it is indeed not fully characterized… Some diagrams open fine, one was converted from UML Composite Structure Diagrams to UML-RT Capsule Structure Diagrams, and some don’t open with an exception raised. I would at least expect come consistency. I will raise a bug for the exception. I will also try to further characterize the issue, but that might prove difficult without some hint that might be gleaned from the exception.

See more inline below.


Sincerely,

Charles Rivet
Senior Product Manager
charles@xxxxxxxxxxxxx

On 2016.05.25, at 10:16 , Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

I just tested the case with 0.7.2 (not tested any of the earlier versions). And I am able to open the capsule structure diagram for that model at least without exceptions. So it does not seem to be a general issue (at least not with diagrams created with 0.7.2).

Please also be careful with the terminology. If the diagram needs to be recreated it is not a "Composite Structure Diagram" on the New Diagram menu that shall be used, it is "UML-RT Capsule Structure Diagram" that shall be selected. And preferably one should also manually ensure that the name of the diagram is empty. By default when creating a diagram in this way from the "New Diagram" menu it gets an explicit name. Normally the capsule structure diagram is left unnamed, so that the diagram name label is automatically picked up from the related capsule's name.

<cr>
I get a different behavior when I created a UML-RT Capsule Structure Diagram. The name shown in the dialog is "NewUML-RTCapsuleStructureDiagram”, not empty. If I clear the name, leaving the field empty, and then click OK, it creates a diagram named "NewUML-RTCapsuleStructureDiagram” and that’s what is shown in both the model explorer and the tab at the bottom of the editor.
​I was a bit unclear. Yes, when you create a new capsule diagram, then currently the default name of the diagram will be as you say​
 
​"NewUML-RTCapsuleStructureDiagram", and even if you "unname" in the dialog it still gets this default. What I meant was that *after* creation, you manually have to "unname", i.e. clear the name, e.g. in the properties view, to get the automatic naming to happen. We should probably write a Bugzilla for this case, and ensure that whenever you use the New Diagram > ​UML-RT Capsule Structure Diagram, then the naming dialog should not appear, and the default name should simply be left unnamed, i.e. to be consistent with the behavior when the capsule structure diagram is being created automatically when creating a capsule.

Is the automatic name display for diagrams (views?) implemented throughout the tool? Given the whole hyperlink infrastructure provided by Papyrus, I could easily see (and I have used) linking from multiple locations to a single, related diagram. If this automatic display of unnamed diagrams is not implemented throughout, creating these hyperlink would become more difficult as there would be many unnamed views in the hyperlink selection dialog.
​As I understand it, it should. I tested the hyper link creation case you mentioned, and yes, in the selection dialog the automatic name is displayed. I guess Remi have to comment that the automatic label provider for the diagram is used consistently throughout the tool.​
 

Current config:
<Screen Shot 2016-05-25 at 11.59.51.png>
</cr>


/Peter Cigéhn

On 25 May 2016 at 15:59, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
Just a note for everyone that if you have old Papyrus-RT models that use composite structure diagrams for the capsules, these will result in an exception if you try to open them.

The workaround is easy: delete the CSD and create a new UML-RT Capsule Diagram. Note that the default layout is currently suboptimal and needs to be adjusted, but at least it’s easier than recreating the whole thing manually.

I realize that few people will have created models with Papyrus-RT 0.7.*, so there will have to be an entry in the release note explaining the workaround.

Before I create a bug about this, I would like to know if it is possible to do something about this? I suspect that this may not be a trivial fix (but I am hoping to be wrong). Given the time remaining before release, the potentially low number of people/models affected, and the simplicity of the workaround, I could consider only relying on the workaround from the release note.


Sincerely,

Charles Rivet
Senior Product Manager
charles@xxxxxxxxxxxxx


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev



_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev



Back to the top