| --- | --- |
| Bugzilla Link | 522257 |
| Status | NEW |
| Importance | P3 enhancement |
| Reported | Sep 13, 2017 13:56 EDT |
| Modified | Dec 19, 2017 08:06 EDT |
| See also | 459606, 522256 |
| Reporter | Ed Willink |
Description
Probably the most common problem for OCL UML users is that they neglect to specify an explicit Profile URI. Not a problem in UML, not even possible in UML 2.4. But in Eclipse UML, a Profile implies an embedded EPackage which has an auto-generated changing nsURI. Consequently OCL is struggling to correlate a variety of run-time EPackages with nsURIs and specification UML Profile without URIs. When the correlation fails users get strange obscure Constraint malfunctions.
If the UML Profile URI is explicit, UML2Ecore re-uses it and everything is easy.
Suggest a warning validation in UML for at least a missing URI on a Profile.
Possibly also a warning for a missing URI on a Model.
| --- | --- | | Bugzilla Link | 522257 | | Status | NEW | | Importance | P3 enhancement | | Reported | Sep 13, 2017 13:56 EDT | | Modified | Dec 19, 2017 08:06 EDT | | See also | 459606, 522256 | | Reporter | Ed Willink |
Description
Probably the most common problem for OCL UML users is that they neglect to specify an explicit Profile URI. Not a problem in UML, not even possible in UML 2.4. But in Eclipse UML, a Profile implies an embedded EPackage which has an auto-generated changing nsURI. Consequently OCL is struggling to correlate a variety of run-time EPackages with nsURIs and specification UML Profile without URIs. When the correlation fails users get strange obscure Constraint malfunctions.
If the UML Profile URI is explicit, UML2Ecore re-uses it and everything is easy.
Suggest a warning validation in UML for at least a missing URI on a Profile.
Possibly also a warning for a missing URI on a Model.