Community
Participate
Working Groups
0. Adopt new template structure (move implementation templates under impl/, public out of xpt/) 1. Move extensions from ConstraintProvider.xpt to more general location (extensions.xpt) 2. Try to avoid IClientSelector unless inevitable (in favor of enablement tag) 3. Find out why isInDefaultEditorContext returns true for any object that is not View 4. Uses of semanticCtxIdMap look suspicious, need better approach 5. Need to check release build if schema doc for org.eclipse.emf.validation.constraintBindings fixed in respect to qualified class name of IClientSelector (which is not internal right now, though spec says it is) More to follow, I suppose
Delivered refactoring with explicit context entity (GenAuditContext) in the GMFGen model (to avoid by-context-id grouping), sematicCtxIdMap (4) gone in favour of explicit visualID check. Lite runtime should reuse most of the stuff generated in full runtime - looks like there's not too much difference, except for few subtleties that might be handled with better structuring of the templates.
Created attachment 95944 [details] Maybe you could find helpful these migration changes to support provided refactoring
(In reply to comment #2) Migration was delivered into CVS.
(In reply to comment #0) While working on bug #228913, item 4, ValidationProvider was significantly refactored to inject java placeholders right into validate() method of appropriate AbstractModelConstraint.
ValidationAction is no longer contributed through ContributionItemProvider, regular jface's IEditorActionBarContributor does that, instead.
[GMF Restructure] Bug 319140 : product GMF and component Templates was the original product and component for this bug
