[sedward]

Hi. I have the following situation when using UML1 to model XML schemas…

In the Outline (Package-Centric) view, I have the following:

+ Model (Name is blank, Type is Model)
+ PackageName1
+ PackageNameA
+ Class
+ Class
+ PackageNameB
+ Class
+ Class
+ PackageNameC
+ Class
+ Class
+ PackageNameD
+ ClassLA
+ Attribute maxLength
+ ClassXX
+ Attribute maxLength
(anon Generalization)
+ PackageName2
+ ClassInt
+ ClassString
(anon Generalization)

What I want to do is move the (anon Generalization) currently under PackageName2 to become under ClassLA within PackageNameD instead, so that it is modeled exactly like the (anon Generalization) that is currently under ClassXX within PackageNameD.

The (anon Generalization) for ClassLA was created when I used the Class Diagram Tool. I put ClassLA in the diagram. I then put ClassString in the diagram. I then selected the New Generalization icon and connected a line from ClassLA to ClassString. When I did that, the (anon Generalization) showed up under PackageName2 with the following properties. (Parent = ClassString, Child = ClassLA, NameSpace = PackageName2). I’d like to change the NameSpace from PackageName2 to Class: ClassLA — however the dropdown for the NameSpace entry only allows me to select Model <untitled>.

How do I do this?

Note: The (anon Generalization) under ClassMA was achieved when I originally reverse engineered an old XMI model into MyEclipse as UML1. I am now adding additional classes, and want them to be modeled the same way, but I find no way to “move” the (anon Generalization) that was created under PackageName2 to the ClassLA that is currently within PackageNameD under PackageName1.

Attachments:

You must be logged in to view attached files.

[sedward]

Note, the indentations in my example outline view did not go across with my posting.

Re-publishing that part using dashes to show…

+ Model (Name is blank, Type is Model)
—+ PackageName1
——+ PackageNameA
———+ Class
———+ Class
——+ PackageNameB
———+ Class
———+ Class
——+ PackageNameC
———+ Class
———+ Class
——+ PackageNameD
———+ ClassLA
————+ Attribute maxLength
———+ ClassXX
————+ Attribute maxLength
————(anon Generalization)
—+ PackageName2
——+ ClassInt
——+ ClassString
——(anon Generalization)

[support-tony]

sedward,

Sorry you are seeing this problem. I could reproduce it and have raised a bug report for it. However, one of your screenshots seems to show the namespace corrected. Did you do this just by typing in the correct namespace to get the screenshot?

I was only able to correct it persistently by exporting the model to an xmi file, then fiddling with the XML by altering the namespace of the generalization and then moving it to a new Foundation.Core.Namespace.ownedElement element within the class definition that should own it. This xmi file can then be imported to a new diagram.

I hope this is of some help.

[sedward]

Thanks Tony for your reply. My screenshot was manipulated to try and be sure I could clearly articulate the problem. I definitely have no ability to pick the namespace that I desire in the dropdown, which I think is the root of the problem.

Thank you for submitting a bug report. I would really like to see this become a priority for fixing. (Hopefully the solution could be as simple as allowing the Namespace dropdown to let you traverse “up” the hierarchy, and then back “down” the hierarchy to where I want it to go. Or even better, an ability to drag and drop the (anon Generalization) from its current location to where I would like it to really exist in the outline view tree.)

It doesn’t help me now…but I am hoping the bug could be fixed soon and letting me know.

Thanks.

[support-tony]

sedward,

Thanks for the suggestion. I’m afraid I can’t say when this will be fixed but I appreciate it is a problem for you and will make that point.

I don’t suppose that the manual workaround I mentioned is any good? If you have many such generalizations, I guess it would be a pain to manually fix them all this way.

[sedward]

Hi Tony:

Unfortunately, the manual workaround you suggested is totally unfeasible for 2 reasons:

1.) I have about 57 newly introduced classes with this problem, and manually searching for and moving each (anon Generalization) to it’s proper parent class would be extremely time consuming…as well as very risky. If I happen to make a mistake in assigning the “xmi.###” reference value for each namespace, I could really mess up the model. (Scanning through and manually updating a 6MB XMI file is a lot more risky than a nice, visual, drag and drop tool that allows me to see the results of my changes, and handles all the cross-referencing in the background.

2.) Even more unfeasible is the fact that exporting the UMR file to XMI, and then later importing the changed XMI file back to UMR will cause the LOSS of well over 100 Class Diagrams I currently have drawn in the model. Your tool does not keep the diagrams that were created, and I would have to go back and re-build every single diagram again in my model.

Hopefully the above two reasons will also help you in getting a fix prioritized for me.

Thanks again for your help.

[support-tony]

sedward,

Fair enough; I guessed the workaround may not be appropriate. I’ve let development know about the importance to you but I can’t comment on how the work gets prioritized for future releases.

I’m very sorry for the inconvenience.

[sedward]

It’s been 5 months since I reported this issue. You mentioned you would forward the issue to development for consideration in a future release, so I was wondering if you could provide a status on its priority. This is still an important issue I would like to see resolved.

Thanks!

[Brian Fernandes]

sedward,

We were unable to prioritize this issue earlier. The dev team is investigating this now and I have targeted it for the first maintenance release of 2013.

Sorry for the delay and inconvenience caused.

[Author]

Posts