Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327956

Summary: Seriously Out of date OCL Validation example
Product: [Modeling] EMF Services Reporter: Ed Willink <ed>
Component: ValidationAssignee: EMF Services Validation inbox <emfservices.validation-inbox>
Status: CLOSED MOVED QA Contact:
Severity: normal    
Priority: P3 CC: pierre-charles.david
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:
Attachments:
Description Flags
Documentation and example improvements none

Description Ed Willink CLA 2010-10-15 16:38:45 EDT 
The Developers's Guide continues to encourage the use of OCL embedded in XML CDATA sections. This was necessary with Eclipse 3.2.

Eclipse 3.3, MDT/OCL 1.1 introduced EMF codegen for OCL from EAnnotations that could be maintained within the Sample Ecore Editor, and could be activated from the generated Java model.

Eclipse 3.6, EMF 2.6 introduced validation delegates which MDT/OCL 3.0 exploited to again support OCL in EAnnotations, support activation from Java models, or dynmamic activation via eInvoke.

It is not clear that the oruginal approaches still work. It is certainly unhelpful to describe them without accompanying warnings and pointers to new approaches.

A redirection to http://127.0.0.1:49350/help/topic/org.eclipse.ocl.doc/tutorials/oclinecore/oclInEcoreTutorial.html would be helpful.
Comment 1 Ed Willink CLA 2012-05-25 11:26:38 EDT 
Created attachment 216292 [details]
Documentation and example improvements
Comment 2 Pierre-Charles David CLA 2022-05-14 09:53:21 EDT 
Eclipse EMF Validation is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/emf-validation.

If this issue is relevant to you and still present in the latest release:

* Create a new issue at https://github.com/eclipse/emf-validation/issues/.
  * Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  * In the GitHub description, start with a link to this bugzilla ticket
  * Optionally add new content to the description if it can helps towards resolution
* Update bugzilla ticket
  * Add to "See also" property (up right column) the link to the newly created GitHub issue
  * Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  * Set status as CLOSED MOVED

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for EMF Validation will be archived and made read-only.
Comment 3 Ed Willink CLA 2022-05-14 15:25:38 EDT 
Surely ALL Bugzilla are to be MOVED since all must be searchable in the single ticket-space?
Comment 4 Pierre-Charles David CLA 2022-09-04 08:32:04 EDT 
Replaced by https://github.com/eclipse/emf-validation/issues/12