http://forums.visual-paradigm.com/posts/1.html JForum - http://www.jforum.net
XMI export doesn't keep polish national characters and replaces them to sequences of type \uXXXX, e.g.:

rodzaje płatności

is replaced with:

rodzaje p\u0142atno\u015bci

It causes some problems with exporting to MDA tools.

Regars,
Jacek]]> http://forums.visual-paradigm.com/posts/2341#18650.html http://forums.visual-paradigm.com/posts/2341#18650.html There is another issue - when exporting to XMI with UML2 option, multiplicities * (for roles or attributes) are represented as:



When importing model to eclipse they are recognized as 1.
So I have to use 0..* to have correct multiplicities, that are represented as two elements:




There is no semantic difference between * and 0..* and * is shorter. Maybe * should be represented the same way, as 0..*

Regards,
Jacek
]]> http://forums.visual-paradigm.com/posts/2341#18652.html http://forums.visual-paradigm.com/posts/2341#18652.html http://forums.visual-paradigm.com/posts/2341#18655.html http://forums.visual-paradigm.com/posts/2341#18655.html Jacenty wrote:

The third issue - when importing to eclipse, elements haven't stereotypes and tagged values, assigned to them in VP.

We have observed this same problem-- it is because the application of stereotypes in UML2 is handled through profiles, which VP doesn't yet support, if I understand correctly. I've been unable to import XMI files defining profiles (authored in Eclipse) into VP-UML, for the same reason, I believe.

Jick, could you please clarify? Are there plans to add profile support to VP, in accordance with the latest versions of UML2? We deal with stereotypes and tagged values a great deal and it would be nice not to have to come up with another mechanism in order to get full "round-trip" compatibility.

Thanks,
Ellen]]> http://forums.visual-paradigm.com/posts/2341#18656.html http://forums.visual-paradigm.com/posts/2341#18656.html
Thank you for the posts. We will investigate the problems and get back to you.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#18660.html http://forums.visual-paradigm.com/posts/2341#18660.html
This has been fixed, but the fix will be available in the coming version. Do you want to try it? If yes, I can arrange an early access release for you.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#18663.html http://forums.visual-paradigm.com/posts/2341#18663.html I'll be busy next week, but then I'd like to try it.

Thank you,
Jacek]]> http://forums.visual-paradigm.com/posts/2341#18664.html http://forums.visual-paradigm.com/posts/2341#18664.html
The next version may be released by the end of the next week. :-)

Take your time.

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#18666.html http://forums.visual-paradigm.com/posts/2341#18666.html We have the same problem, when exporting the XMI with french characters :
The "é" charcter is replaced in the xmi by "\u00e9".
Is there any correction of this issue available.

Many Thx
Regards,]]> http://forums.visual-paradigm.com/posts/2341#18675.html http://forums.visual-paradigm.com/posts/2341#18675.html
Thanks for the info. I would also be very interested in evaluating the fix ASAP-- please keep me posted!

- Ellen]]> http://forums.visual-paradigm.com/posts/2341#18676.html http://forums.visual-paradigm.com/posts/2341#18676.html
In the coming version, we will let user select an encoding for the XMI, which will solve this problem.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#18689.html http://forums.visual-paradigm.com/posts/2341#18689.html Thx for your replay. Is there any patch correcting this issue. i understood reading the forum that it's an old issue.
May we know when this new version will be released. and be posted if possible.
Many thx
Regards, ]]> http://forums.visual-paradigm.com/posts/2341#18694.html http://forums.visual-paradigm.com/posts/2341#18694.html
I regret that there is patch available for this fix. However, this will be available in the coming version, which will be released very soon. We expect to roll out the new version by the end of this week.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#18697.html http://forums.visual-paradigm.com/posts/2341#18697.html many Thanks.

reagrds, ]]> http://forums.visual-paradigm.com/posts/2341#18699.html http://forums.visual-paradigm.com/posts/2341#18699.html
Thanks for the information on the upcoming release. Will this include the fixes to the Eclipse UML2 export as well? (That's the main issue that would prevent us using VP-UML at this time.)

Thanks,
Ellen]]> http://forums.visual-paradigm.com/posts/2341#18706.html http://forums.visual-paradigm.com/posts/2341#18706.html
Sure. The fix will cover UML2 Export as well.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#18709.html http://forums.visual-paradigm.com/posts/2341#18709.html
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 <> ), 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]]> http://forums.visual-paradigm.com/posts/2341#18801.html http://forums.visual-paradigm.com/posts/2341#18801.html
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]]> http://forums.visual-paradigm.com/posts/2341#18807.html http://forums.visual-paradigm.com/posts/2341#18807.html 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
]]> http://forums.visual-paradigm.com/posts/2341#18815.html http://forums.visual-paradigm.com/posts/2341#18815.html
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
]]> http://forums.visual-paradigm.com/posts/2341#18822.html http://forums.visual-paradigm.com/posts/2341#18822.html
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]]> http://forums.visual-paradigm.com/posts/2341#18826.html http://forums.visual-paradigm.com/posts/2341#18826.html
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]]> http://forums.visual-paradigm.com/posts/2341#18831.html http://forums.visual-paradigm.com/posts/2341#18831.html
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:

I don't know, which way are tagged values represented.

Regards,
Jacek]]> http://forums.visual-paradigm.com/posts/2341#18833.html http://forums.visual-paradigm.com/posts/2341#18833.html 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,]]> http://forums.visual-paradigm.com/posts/2341#18838.html http://forums.visual-paradigm.com/posts/2341#18838.html
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 and when "*" is selected as multiplicity.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#18846.html http://forums.visual-paradigm.com/posts/2341#18846.html There is another issue - interfaces are exported as classes with <> stereotype, since eclipse expects elements of type interface.

Regards,
Jacek]]> http://forums.visual-paradigm.com/posts/2341#18862.html http://forums.visual-paradigm.com/posts/2341#18862.html
Thank you for your post. I will ask our engineers to fix it up.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#18863.html http://forums.visual-paradigm.com/posts/2341#18863.html
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]]> http://forums.visual-paradigm.com/posts/2341#18885.html http://forums.visual-paradigm.com/posts/2341#18885.html Jick wrote:

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]]> http://forums.visual-paradigm.com/posts/2341#18887.html http://forums.visual-paradigm.com/posts/2341#18887.html
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]]> http://forums.visual-paradigm.com/posts/2341#18897.html http://forums.visual-paradigm.com/posts/2341#18897.html Jick wrote:

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

Jick,

You are correct in that stereotypes defined in models are not "valid" in UML2-- stereotypes must be defined in a profile, after which the profile can be applied to the model and then the stereotypes can be applied to elements.

So, I suppose the question is: what are the plans for VP-UML to support profiles when importing/exporting to Eclipse UML2 via XMI? I've tried to import my profile XMI file and VP-UML does not appear to support it.

Thanks,
Ellen]]> http://forums.visual-paradigm.com/posts/2341#18899.html http://forums.visual-paradigm.com/posts/2341#18899.html
Thank you for your clarification. I'll discuss with our engineers and reply you as soon as possible.

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#18904.html http://forums.visual-paradigm.com/posts/2341#18904.html Stereotypes represented as annotations are enough for me now, but I hope it will be full support in the future.

This article shows, how to define and apply profiles in eclipse:
http://www.eclipse.org/modeling/mdt/uml2/docs/articles/Introduction_to_UML2_Profiles/article.html

Regards,
Jacek]]> http://forums.visual-paradigm.com/posts/2341#18908.html http://forums.visual-paradigm.com/posts/2341#18908.html
Thank you for your feedback. We decided to support Profile. But this may take some time for development. We'll try our best to send you early access release that include this functionality in the next week. Let's keep in touch.

Have a nice weekend!

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#18922.html http://forums.visual-paradigm.com/posts/2341#18922.html I think it's right decision.

Thanks,
Jacek]]> http://forums.visual-paradigm.com/posts/2341#18924.html http://forums.visual-paradigm.com/posts/2341#18924.html
The support of profile export/import UML2 XMI is about ready. Do you want to try it out? I can arrange an early access release for you by request.

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#19055.html http://forums.visual-paradigm.com/posts/2341#19055.html Thx for your Answer. But the solution you provide seems to be on version 6.1. We're on 6.0 (Sp2 last update) version.
Is there, please, any solution without changing version.
And last question , to upgrade the version, is a new licence needed?

Many Thx, Ragards]]> http://forums.visual-paradigm.com/posts/2341#19098.html http://forums.visual-paradigm.com/posts/2341#19098.html
I regret that the change will be made available to the new version, probably VP Suite 3.1 Service Pack 1. In order to enjoy version upgrades, please purchase maintenance. The following page describes the content of software maintenance:
http://www.visual-paradigm.com/shop/maintenance.jsp

With maintenance, you will receive version upgrades and technical supports. You may purchase maintenance by visiting the Maintenance page of your customer account.

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#19105.html http://forums.visual-paradigm.com/posts/2341#19105.html Jick wrote:

Hello Jacenty and ebadgley, The support of profile export/import UML2 XMI is about ready. Do you want to try it out? I can arrange an early access release for you by request. Best regards, Jick

Jick,

Thanks for this-- I would be very interested! I am still operating on evaluation licenses while we determine if VP-UML is right for our needs (and this UML2 compatibility is very important for that) but I would definitely like to see the new release if possible.

(Sorry for the late reply; somehow my email notification of new posts got turned off...)

- Ellen Badgley]]> http://forums.visual-paradigm.com/posts/2341#19112.html http://forums.visual-paradigm.com/posts/2341#19112.html
I've sent you an email about the early access release. Please have a try. Feel free to let me know if there are any questions.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19127.html http://forums.visual-paradigm.com/posts/2341#19127.html
I have investigated the early release you sent me and it is a MASSIVE step in the right direction! I was able to get a model with an applied profile to import and export without problems. I haven't finished testing everything yet but this gives me lots of hope that we will be able to use VP-UML-- without profile support it didn't seem that there was full round-trip compatibility with Eclipse UML2 as claimed.

I did notice one thing: in my profile, I have several stereotypes specified, but not all of them are applied to elements in my model. I noticed that only the applied stereotypes were imported into VP-UML. Was this the developers' intention?

Thanks again for your responsiveness and for your help!

- Ellen]]> http://forums.visual-paradigm.com/posts/2341#19143.html http://forums.visual-paradigm.com/posts/2341#19143.html
Glad that you like it. I'll discuss with our engineers and reply you as soon as possible.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19146.html http://forums.visual-paradigm.com/posts/2341#19146.html
I've just sent you an email with a patch that fixes the problem of not considering non-applied stereotype. Please have a try. :-)

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19161.html http://forums.visual-paradigm.com/posts/2341#19161.html I just read the information about adding profile support to VP. How can I download this version?

Regards,
Jacek]]> http://forums.visual-paradigm.com/posts/2341#19226.html http://forums.visual-paradigm.com/posts/2341#19226.html
I have sent you an Email. Please check.

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#19238.html http://forums.visual-paradigm.com/posts/2341#19238.html
I am happy to inform you all that VP Suite 3.1 Service Pack 1 has been released with the support of UML2 profile. If you are running VP Suite 3.1, you can advance to Service Pack 1 by running the Updater inside the bin folder of VP Suite installation directory.

As always, feel free to let me know if there are any questions.

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#19435.html http://forums.visual-paradigm.com/posts/2341#19435.html
Is there a plan to include this Profile Support eventually in anything other than VP Suite? We don't need the features of VP Suite other than VP-UML.

Thanks,
Ellen]]> http://forums.visual-paradigm.com/posts/2341#19770.html http://forums.visual-paradigm.com/posts/2341#19770.html http://forums.visual-paradigm.com/posts/2341#19772.html http://forums.visual-paradigm.com/posts/2341#19772.html
This is a misunderstanding. VP Suite 3.1 includes VP-UML 6.1, SDE 4.1, DB-VA 4.1, BP-VA 2.1 and AG 1.1. When I said VP Suite 3.1 SP 1 has released with the support of UML2 profile, all the included products, including VP-UML 6.1 SP 1, include the change. Therefore, you can advance to VP-UML 6.1 Service Pack 1 to enjoy the support of UML2 profile.

What are the issues with importing UML2? We tried your file and can import without problem.

Best regards,
Jick]]> http://forums.visual-paradigm.com/posts/2341#19778.html http://forums.visual-paradigm.com/posts/2341#19778.html
Thanks so much for the clarification. We had already placed an order for some Professional licenses of VP-UML, not the full VP Suite-- so I just wanted to confirm that we had ordered the right thing (given that you talked about VP Suite above)!

As for the importing problem, here's a summary:
1) Open VP-UML.
2) On the File menu, select "Import->XMI File".
3) Browse to the "nas_v1.8.1_packages.uml" file (which uses the profile defined in the other file).
4) The following message appears almost instantly:

[error 11:26:20]XMI file is not supported, xmi-version: 2.1, exporter: not found, exporter-version: not found

I am running Version 6.1, Build 20070801 (this was the version you so kindly provided to us earlier to demonstrate the fix for the Profile problems).

Thanks again for your continued help. We have been very impressed with VP's service and responsiveness to issues like this and are looking forward to working with you further.

- Ellen]]> http://forums.visual-paradigm.com/posts/2341#19784.html http://forums.visual-paradigm.com/posts/2341#19784.html
You are welcome. We appreciate your feedback. :-)

Build 20070801 is too old. Please advance to VP Suite 3.1 Service Pack 1 which have the fix of the problem you mentioned. You can run the update program inside the bin folder to advance to the latest version.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19785.html http://forums.visual-paradigm.com/posts/2341#19785.html
- Ellen]]> http://forums.visual-paradigm.com/posts/2341#19789.html http://forums.visual-paradigm.com/posts/2341#19789.html
I tested the model I sent previously using the new build. It imported successfully! However, I still observe a couple of problems:

1) Our Tagged Values do not appear to be imported. In our profile, tagged values are defined as Properties on all of the stereotypes. There is a list of about 25 tagged values that should be attached to the "Bundle" stereotype for Packages, for example. When I import the model into VP-UML, I don't see any of the tagged values-- the list is completely blank when I open it up on the Specification panel.
(As an example, the first package-- Aeronautical Aids to Navigation-- correctly has our "Bundle" stereotype applied, but there should be about 25 tagged values and I don't see any of them.)

2) I am seeing most of our "unused" stereotypes imported from the profile. Thanks for the fix there. However, it still looks like a couple of them are missing:
- ApplicationSchema, Bundle and Leaf stereotypes should extend Package; ApplicationSchema is missing.
- Type, FeatureType, MetaClass, and InfoType stereotypes should extend Class; MetaClass and InfoType are missing.
- Eclipse has a PrimitiveType element, and we have a BasicType stereotype that extends that. BasicType is showing up on Class...
- The Eclipse DataType element is extended by our own custom DataType and Union stereotypes. I don't see either of those in the VP-UML imported model.
- The Eclipse Enumeration element is extended by our own Enumeration and CodeList stereotypes. I don't see either of those.
- Attribute and AssociationRole stereotypes extend Property-- these are both OK.
- Our custom ASsociation extending the Association element is OK.
- Our PackageDependency extending Dependency is OK.
- Our InheritRelation extending Generalization is OK.
- We also define an EnumerationLiteral stereotype extending the Eclipse EnumerationLiteral element-- this is missing.

I know the internal metamodel you are using is still UML, but it looks like some of the internal workings or representations of that metamodel is different enough between VP-UML and Eclipse that some things aren't translating clearly...So I was wondering: Can this be fixed so that all of the stereotypes do come over cleanly? and, Is there a way to store the appropriate information so when writing the model back to Eclipse/UML2-compatible XMI 2.1, the translation works the other way as well?

Thanks,
Ellen Badgley
- ]]> http://forums.visual-paradigm.com/posts/2341#19794.html http://forums.visual-paradigm.com/posts/2341#19794.html
We will review your feedback as soon as possible. Thank you.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19840.html http://forums.visual-paradigm.com/posts/2341#19840.html
All the listed problems are fixed. Please download and install the patch at:
http://files3.visual-paradigm.com/200710/Patch/sp1_20071101w/VP_Suite_Windows_3_1_sp1_20071101w.exe

Hope this helps. Please feel free to let me know if there are any questions.

Have a nice weekend!

Best regards,
Jick ]]> http://forums.visual-paradigm.com/posts/2341#19846.html http://forums.visual-paradigm.com/posts/2341#19846.html
Thanks for the amazingly prompt fix! I have tested and the patch does indeed fix the problems I mentioned before. Great work as usual! However, I did notice some additional issues when importing our model and profile:

1) Some additional stereotypes are showing up in the VP-UML model.
- InheritRelation (Class) in addition to Inherit Relation (Generalization)
- Association Role (AssociationEnd) and AssociationRole (AssociationEnd) in addition to Association Role (Property)
- Attribute (Attribute) in addition to Attribute (Property)
- BasicType (Property) in addition to BasicType (Class)
- PackageDependency (Dependency) in addition to Package Dependency (Dependency).
- Association (Association), Bundle (PackagE), Leaf (Package), Application Schema (Package), Enumeration (Enumeration), EnumerationLiteral (EnumerationLiteral), ISOType (DataType), InfoType (Class), MetaClass (Class), Type (Class), and Union (DataType) are all just fine.
It looks like two different things are happening here. Some of our stereotypes with spaces in the names (Package Dependency, Association Role) are having those spaces dropped and a new stereotype created accordingly (but without the proper tagged values attached to the original stereotype). Additionally, some new stereotypes are getting created that extend different UML metamodel elements from the original ones-- Attribute (Attribute) vs. Attribute (Property) is an example. Again, the new stereotype does not contain the tagged values of the old.

2) Where is Datatypes.Class coming from? It is stereotyped BasicType and primitive, and is used as the type for most of the attributes in the model. The attributes should instead have a type of Datatypes.TextLexUnconstrained...

3) Some stereotypes/tagged values are not being applied:
- TextLexUnconstrained (in the Datatypes package) is supposed to be stereotyped <> and have the appropriate tagged values-- it doesn't.
- The <> dependency relationships (there is at least one in most packages) are stereotyped <> instead of <>. For this reason, there are no tagged values attached to them. This appears to be a situation where the second, incorrect stereotype is getting used instead of the correct stereotype.
- The same thing as above appears to be happening with dependencies, where the <> stereotype is getting used instead of the correct <>. For this reason the tagged values from <> don't show up.
- The same thing is happening with all attributes, which are getting stereotyped Attribute (Attribute) instead of Attribute (Property).

4) Constraints within our model don't seem to show up. For example, Elevation.Hypsography.SpotElevation has one constraint on its geometry that I don't see in the VP-UML project.

If there are changes we can make to our Profile that will make the round-trip to and from UML2 easier, it is no problem to do that. I suspect that VP-UML's implementation of the UML 2.x metamodel may have some significant differences to Eclipse's implementation that are causing some of the discrepancies here. We'd simply like to get "lossless" round-trip translation from VP-UML to Eclipse and vice-versa up and running.

Also, please let me know if you would prefer to continue our discussion outside the forums, as I've monopolized this topic recently (thanks to Jacenty for allowing me to do so).

Thanks again for the great support,
Ellen]]> http://forums.visual-paradigm.com/posts/2341#19867.html http://forums.visual-paradigm.com/posts/2341#19867.html
No problem. We can continue here. Could you send an XMI file saved from UML2?

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19876.html http://forums.visual-paradigm.com/posts/2341#19876.html
This was done with the exact same XMI file that I posted as an attachment to my 10/24/2007 post (nas_v1.8.1_packages.uml and the profile file).

Thanks,
Ellen]]> http://forums.visual-paradigm.com/posts/2341#19889.html http://forums.visual-paradigm.com/posts/2341#19889.html
Wait, I apologize: I misspoke! The correct file is large-- can you provide me an email address so I can send it to you?

Thanks,
Ellen]]> http://forums.visual-paradigm.com/posts/2341#19890.html http://forums.visual-paradigm.com/posts/2341#19890.html
Sure. This is my Email address:
jick@visual-paradigm.com

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19892.html http://forums.visual-paradigm.com/posts/2341#19892.html
I've received our file. Will investigate the reported problems.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19939.html http://forums.visual-paradigm.com/posts/2341#19939.html
As I know most of the reported problems have been fixed. We will send you a patch on Monday. If you need the fix urgently, I could arrange a patch for you (which contains most fixes).

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19950.html http://forums.visual-paradigm.com/posts/2341#19950.html
Wonderful! Monday is completely fine with me. Thanks!

- Ellen]]> http://forums.visual-paradigm.com/posts/2341#19962.html http://forums.visual-paradigm.com/posts/2341#19962.html
Here is the patch download URL:
http://files3.visual-paradigm.com/200711/Patch/sp1_20071116b/VP_Suite_Windows_3_1_sp1_20071116b.exe

Here is the information about the fixes:

1)
Fixed

2)
Datatypes.Class is the "PrmitiveType" of TextLexUnconstrained (because "DataType" of TextLexUnconstrained is imported first, so "DataType"'s name is correct),
ref to the above task, please ask user delete DataType.

3)
Regarding "TextLexUnconstrained ", in the package "Datatypes", there are 2 elements named "TextLexUnconstrained". They are:
<packagedElement xmi:type="uml:DataType" xmi:id="_soANPIMkEdyfDNMZNSEuWg" name="TextLexUnconstrained"/>
<packagedElement xmi:type="uml:PrimitiveType" xmi:id="_soANPYMkEdyfDNMZNSEuWg" name="TextLexUnconstrained"/>
one is "DataType", another one is "PrimitiveType".

However, after import to VP-UML, both become "Class". and Class does not allow duplicate name. So one of the model's name become "Class"
By checking the xmi, no element is referencing:
<packagedElement xmi:type="uml:DataType" xmi:id="_soANPIMkEdyfDNMZNSEuWg" name="TextLexUnconstrained"/>
Therefore, we suggest you delete it first.

And for the stereotype "BasicType, since the "BasicType" stereotype's baseType is "PrimitiveType" in XMI, we have fixed to read the baseType as "Class" insteadof "PrimitiveType"

Regarding "Attribute", it is the same as the "PrimitiveType" issue reported under problem 2, and should be read as "Class".

Since we do not have "Property", we will create 2 stereotypes if the baseType is "Property" (one for "Attribute", one for "AssociationEnd", both stereotypess have the taggedValues if exists in xmi)

4)
Fixed

Hope this helps.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#19986.html http://forums.visual-paradigm.com/posts/2341#19986.html
Thanks! I'm checking it out now.

In the meantime, we observed a problem with Association End multiplicity with a different file. There was an association for which both ends had [0..1] multiplicity. In the Eclipse UML2 file, both the Lower and Upper bounds for multiplicity are assumed to be 1 if they are not set otherwise. This meant that in our file, each Property defining one of the association ends had a single "child", a " 0", for the lower bound of 0.

When I imported the file into VP-UML, I noticed that the multiplicity for both association ends was getting set to 0. I wonder if the "0" lower bound is getting picked up by VP-UML and used for the total multiplicity, and the implied "1" upper bound is getting ignored.

I hesitate to send you the UML file because I and my group do not "own" it, but if necessary I can come up with a simple one to send you for testing.

Thanks again!

- Ellen]]> http://forums.visual-paradigm.com/posts/2341#20001.html http://forums.visual-paradigm.com/posts/2341#20001.html
We will check the problem and get back to you a.s.a.p. Meanwhile, please have a try to the 4 reported problems. If you have question, feel free to let me know.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#20004.html http://forums.visual-paradigm.com/posts/2341#20004.html
Sorry, problem 4 has not yet been fixed. I will send you a patch again a.s.a.p. Sorry once again.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#20009.html http://forums.visual-paradigm.com/posts/2341#20009.html
Please try again with this hotfix:
http://files3.visual-paradigm.com/200711/Patch/sp1_20071119/VP_Suite_Windows_3_1_sp1_20071119.exe

Hope this helps.

Best regards,
Jick
]]> http://forums.visual-paradigm.com/posts/2341#20136.html http://forums.visual-paradigm.com/posts/2341#20136.html
Sorry I have not responded in quite some time-- I was pulled away to work on another aspect of our project. In the meantime, however, our licenses for VP-UML came through, so waiting paid off! I'm now back looking at our Eclipse exports and VP-UML imports, and would like to do some more troubleshooting of this process with you.

One of the things I have done is to significantly improve the UML2 Profile we are using in Eclipse, including fixing some things I was doing improperly before (and which, no doubt, contributed to some of the problems I was having moving files back-and-forth between Eclipse and VP-UML). The profile is now much more stable and I now have a better handle on what *needs* to happen in Eclipse and VP-UML in the translation process, so hopefully I can provide better descriptions of any issues as they occur.

Using our new profile and Eclipse UML2 utility, I've imported our UML2 file into VP-UML and have begun checking it. Things are looking very good overall, but there are still some issues. The file is large so I would prefer to send it to you via email rather than posting it here (this will also enable me to send both the original *.uml file and the VP-UML project I created from importing it).

The following are the initial things I have observed when importing our new Profile:

1) Tagged values attached to the stereotypes (which now have proper lower-case names!) are not getting imported. Within the Profile Application portion of our *.uml file, I have noticed that these tagged values *are* getting set correctly. The stereotypes do look good and extend the correct base classes.

2) Comments are showing up in the base of the model, instead of attached to the model element they are supposed to be attached to. For example, in the "ISO 19100::ISO/TS 19103 Conceptual Schema Language::Basic Types - Primitive - Numerics" package, the "Vector" has a constraint with an OCL body and a Comment describing the constraint: "The value of the 'dimension' is determined by the length of the 'ordinates' number-array." In the VP-UML project, the Constraint (the OCL) is properly attached to the Vector . However, the Comment shows up in the root of the model, along with all other similar comments.

3) I have noticed when importing a UML2 file which has an applied profile containing stereotypes that the stereotype definitions remain within VP-UML after that project/model is closed. This previously caused me some confusion as I was testing out different versions of our profile, because I ended up with multiple stereotypes with identical names which had different tagged values and definitions. Sometimes it seemed that the wrong "version" of the stereotype was getting applied to a model element. Anyway, I would be interested to know whether or not this is by design. It would seem to me that since stereotypes are defined in a profile, they should be restricted to models with that particular profile applied...If you could please explain some of the philosophy behind this, I'd appreciate it!

Thanks for your continued help!]]> http://forums.visual-paradigm.com/posts/2341#20705.html http://forums.visual-paradigm.com/posts/2341#20705.html
Have you and the support team had a chance to look at the above issues and the files yet?

Thanks!]]> http://forums.visual-paradigm.com/posts/2341#20947.html http://forums.visual-paradigm.com/posts/2341#20947.html