| Author |
Message |
|
2007/07/31 08:29
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
Hi Ellen,
Sure. The fix will cover UML2 Export as well.
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
 |
| |
|
|
2007/08/08 01:30
|
|
|
ebadgley
Joined: 2007/07/27
Messages: 27
Offline
|
|
|
|
Jick,
I've downloaded the evaluation copy of 6.1, but I'm sorry to say I'm still not seeing the desired functionality when it comes to UML2 exporting. Perhaps I'm doing something wrong?
Please take a look at the attached zip file. The .vpp within was initially created by importing a simple model (in UML2/XMI format) from Eclipse. (The model is based on one from the UML2 Tutorial.) I altered it by creating a new Stereotype (simply called <<TestStereotype>> ), then I applied this stereotype to the "Address" class. This worked perfectly within VP-UML.
The .uml file is the result after the model was exported from VP-UML (UML 2.1, "UML2 compatibility" selected). Whereas TestStereotype is still defined within the model, it is no longer applied to the Address class. This was the behavior I was hoping would be present in the new version.
Can you shed any light on this? Perhaps I'm laboring under a misapprehension.
Thanks,
Ellen
| Description |
Test VPP and UML files for Stereotype example |
Download
|
| Filesize |
20 kb
|
| Downloaded: |
104 time(s) |
|
|
|
|
|
| |
|
|
2007/08/08 10:20
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
hi Ellen,
Sorry, I haven't mention that it is only the first and the second problem get fixed. For the third problem, which is the one you spoke of, we are still investigating.
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2007/08/08 18:24
|
|
|
Jacenty
Joined: 2006/11/09
Messages: 73
Offline
|
|
|
|
Hi Jick,
There are any issues in new release:
1. When I use default encoding "windows-1250" and generate xmi file, polish characters are changed with something like escape sequences, but if I choose "other" option, and then "windows-1250" from the combo box, it works well.
2. When importing generated file with eclipse, following error message occurs: Declared encoding "windows-1250" does not match actual one "Cp1250"; this might not be an error.
Import works well after changing the encoding tag from "windows-1250" to Cp1250.
Regards,
Jacek
|
|
|
|
|
| |
|
|
2007/08/09 19:13
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
Hello Jacenty,
We will investigate the problems. For point 2, may I ask you for a sample XMI so that we can reproduce and fix the problem faster? Thank you.
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2007/08/09 21:21
|
|
|
Jacenty
Joined: 2006/11/09
Messages: 73
Offline
|
|
|
|
Hello Jick,
I've attached sample XMI file. It was generated as UML2.
Of course, encoding problem hasn't big priority for me - importing stereotypes and tagged values is much more important.
Regards,
Jacek
| Description |
|
Download
|
| Filesize |
15 kb
|
| Downloaded: |
93 time(s) |
|
|
|
|
|
| |
|
|
2007/08/10 09:02
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
HI Jacek,
I have consulted our engineers, and they told me that windows-1250 should be the same as Cp1250. Would it be UML2's problem that can't accept our file encoded with windows-1250?
Importing stereotypes and tagged values require more changes. I am afraid this won't be supported very soon. But we'll inform you once it is ready.
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2007/08/10 15:44
|
|
|
Jacenty
Joined: 2006/11/09
Messages: 73
Offline
|
|
|
|
Hi Jick,
Before importing model with eclipse I change encoding manually in exported xmi file, and import passes without any problems.
As far as stereotypes are concerned - maybe there is something like half-way solution? I saw quite simple approach - stereotypes were represented as ecore annotations.
Example below shows the Entity stereotype representation:
<eAnnotations xmi:id="_60yc8MQtEdqfR6grBgMgcg" source="http://www.eclipse.org/uml2/2.0.0/UML">
<details xmi:id="_60yc8cQtEdqfR6grBgMgcg" key="Entity"/>
</eAnnotations>
I don't know, which way are tagged values represented.
Regards,
Jacek
|
|
|
|
|
| |
|
|
2007/08/11 01:45
|
|
|
Riadh
Joined: 2007/07/27
Messages: 7
Offline
|
|
|
|
Hi Jlick,
I checked for updates last Week and this and no one was available.
Can you please tell me how to pick the patch resolving French characters issue .
Many thx
Regards,
|
|
|
|
|
| |
|
|
2007/08/13 09:22
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
To Jacek,
Thank you. I will let our engineers know about this.
Best regards,
Jick
To Riadh,
Concerning the encoding issues, please select the correct encoding when exporting XMI. For your case it should be ISO-8859-1. Please see the attached image for more information.
Concerning the multiplicity issue, the UML2 XMI will now export both <lowerValue value="0"...> and <upperValue value="*"...> when "*" is selected as multiplicity.
Best regards,
Jick
Attached Image :
No description given
(16 kb)
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2007/08/13 19:13
|
|
|
Jacenty
Joined: 2006/11/09
Messages: 73
Offline
|
|
|
|
Hi Jick,
There is another issue - interfaces are exported as classes with <<interface>> stereotype, since eclipse expects elements of type interface.
Regards,
Jacek
|
|
|
|
|
| |
|
|
2007/08/13 19:25
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
HI Jacek,
Thank you for your post. I will ask our engineers to fix it up.
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2007/08/14 18:31
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
Hi Jacek,
The problem of incorrectly exported interface as class has been fixed. Please download the patch at:
http://files3.visual-paradigm.com/200708/Patch/6-1-0_20070814b/VP_Suite_Windows_3_1_20070814b.exe
This also includes the fix of the following problem:
| 1. When I use default encoding "windows-1250" and generate xmi file, polish characters are changed with something like escape sequences, but if I choose "other" option, and then "windows-1250" from the combo box, it works well.
|
Now, the default is changed to UTF-8 rather than windows-1250.
Please run the patch and install it by overwriting the existing installation.
Feel free to let me know if there are any questions.
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2007/08/14 21:59
|
|
|
ebadgley
Joined: 2007/07/27
Messages: 27
Offline
|
|
|
|
HI Jacek,
Importing stereotypes and tagged values require more changes. I am afraid this won't be supported very soon. But we'll inform you once it is ready.
Best regards,
Jick
|
Jick,
Thanks again for keeping us updated on this. Can you provide a ballpark estimate for the stereotypes/tagged values changes (i.e. a month, six months, a year)? I apologize for being a "broken record" on this, but we've got some collaborators who are looking for a UML IDE that includes these features, and they have requested that we keep giving them updates.
Thanks,
Ellen
|
|
|
|
|
| |
|
|
2007/08/15 18:48
|
|
|
Jick
Joined: 2005/04/29
Messages: 2880
Offline
|
|
|
|
Hi Jacek and Ellen,
I have discussed with our engineers. They would like to know if your goal is to make Eclipse UML2 able to "know" the stereotype of model. If yes, we wonder if this is valid or not. Please refer to:
http://dev.eclipse.org/newslists/news.eclipse.tools.emf/msg12467.html
Excerpt:
"A stereotype is a UML concept, and EMF (Ecore) is not an implementation of UML. A similar concept in MOF is tags, which are essentially represented in Ecore as annotations."
and we have tried in Eclipse UML2, it seems it's really not stereotype as we can't apply the stereotype.
We'll keep investigating this issue. Please feel free to give any comment about this.
Best regards,
Jick
Attached Image :
No description given
(328 kb)
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
