Bugzilla – Full Text Bug Listing
| Summary: | [EMF-Portfolio] Adding the CDO feature | ||
|---|---|---|---|
| Product: | [Modeling] EMF.EGF | Reporter: | Benoit Langlois <benoit.langlois> |
| Component: | Core | Assignee: | Matthieu Helleboid <matthieu.helleboid> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Benoit Langlois
I've just committed a new plugin : org.eclipse.egf.emf.pattern.cdo This plugin allows to generate CDO Native code in two ways : * In place generation : - transform the genmodel for CDO Native : a parameter allows to set Dynamic or Reflective generation - generate the emf code in the same plugin as usual - also add the org.eclipse.emf.cdo dependency to the model plugin * Additional plugin generation with Factory Override (Thanks to Alex Lagarde for this idea) : - transform the genmodel for CDO Native : a parameter allows to set Dynamic or Reflective generation - generate the emf model Implementation code (xxxImpl.java) in a new plugin (xxx.cdo) - use an EMF Factory Override to take advantage of the CDO Native Implementation code bug fix : when generating cdo native code in an additional plugin, make sure to use cdo genPackages instead of original genPackages in usedGenPackages. It make sense for metamodel using other metamodels. So I also added a check for both cdo generation style, to check that all usedGenPackages are also generated for CDO (or may cause bugs with the eStaticFeatureCount method generation) feature implemented closed/fixed |