search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

[library] oclstdlib is not a useable model #416

Closed eclipse-ocl-bot closed 1 month ago

eclipse-ocl-bot commented 1 month ago

| --- | --- | | Bugzilla Link | 287017 | | Status | CLOSED DUPLICATE of bug 196873 | | Importance | P3 normal | | Reported | Aug 19, 2009 02:28 EDT | | Modified | Jun 26, 2010 10:14 EDT | | Version | 1.3.0 | | Reporter | Ed Willink |

Description

Neither oclstdlib.uml nor oclstdlib.ecore are useable as models.

Neither models the type conformance relationships through generalisation.

oclstdlib.ecore has the much greater problem that classes are modelling with _Class suffix names.

Since these models are not used for code generation, shouldn't they represent the user perspective of the OCL standard library. i.e. correct names and correct relationships?

NB. This probably means that the internal set of Java classes should have a different URI to the Ecore model.

It may be that this just isn't possible.

A Classifier could be introduced, but user classes would not inherit from it and there is no way OclVoid and OclInvalid can inherit from all user classes. Or do we have a load time adjustment so that the loaded models are automatically edited to have the missing relationships?

eclipse-ocl-bot commented 1 month ago

By Ed Willink on Jun 26, 2010 10:14

This bug has been marked as a duplicate of bug 196873