| Summary: | Provide a UML 2.5 Beta examples plugin | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Ed Willink <ed> | ||||||
| Component: | Core | Assignee: | UML2 Inbox <mdt-uml2-inbox> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | ||||||||
| Version: | 4.0.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows Vista | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | 401118 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ed Willink
I don't see how such examples are of general interest to UML2 consumers, especially without first class support for (de)serializing them. Note that native support for UML 2.5 is tentatively planned for the Kepler + 1 (Luna?) release of UML2... The "Importing/Opening xmi file from OMG" thread of 9 Aug 2013 on the UML newsgroup is typical of a user trying to use recent OMG specifications and running into big trouble because there is no way that I know of to define the relevant namespaces. How do I/we help these guys? The newsgroup post didn't have anything to do with namespaces from a newer specification; instead, it had to do with malformed XMI (I replied in the forum to that effect). Thanks. Simple 'fix'. I thought we needed to define new namespaces. Created attachment 235874 [details] Standalone support for UML 2.5 using UML 2.4.1 The attached file may be used to install UML 2.5 support for standalone usage of UML 2.4.1. Note that in XMI252UMLExtendedMetaData.getPackage() else if ("http://www.omg.org/spec/MOF/20131001".equals(namespace)) { return demandPackage(namespace); } else if ("http://www.omg.org/spec/XMI/20131001".equals(namespace)) { return demandPackage(namespace); } suppresses redundant Internet pings; this should be in the standard UMLExtendedMetaData too. |