EEF/Migrating version

← Back to EEF

This page list all the migration process

From v0.8.X to v0.9.X

Migrating models

There was no regressive changes in EEF metamodels in 0.9 version.

Migrating from end-user point of view

• First, relaunch generation. Use the organize imports action of JDT if needed.
• If you have user code lost in *.lost files, use components and views extension mechanism to reintegrate this code. Delete lost files.
• The components providing mechanism have been changed in 0.9. EEF don't use the XXXPackageEditionProvider and XXXPackagePolicyEditionProvider to get controller and editing policies but a generated AdapterFactory instead. Delete theses classes.

• The sample plugin.xml generated file is updated with the new AdapterFactory declaration. Replace old EEF providers declaration by the generated AdapterFactory.

• Finally, update the OpenWizardOnDoubleClick constructor call (if you use wizards). It takes now the adapterFactory to use in parameter.

It works ! If you have any other trouble, see API Changes section or ask on EMFT newsgroup

API changes

The Batch mode in EEF have been redefined. It no longer use clone to compute difference before and after editing, but use ChangeRecorder instead. When opening an editing session in batch mode (basically editing a model element with the EEF wizard), changes are made in live, and if cancel button is used, all changes of the session are undone. This implies major API changes :

• getPropertiesEditionCommand() and getPropertiesEditionObject() are deleted from IPropertiesEditionComponent
• StandardEditingCommand and WizardEditingCommand are created
• WizardEditingOperation is created for EMF Workspace compliance
• EMFListEditUtil (clones manager) is removed

AdapterFactory are now used in order to replace PropertiesEditionProvider and PropertiesEditionPolicyProvider :

• IPropertiesEditionProvider, IPropertiesEditionProviderFactory and IPropertiesEditionPolicyProviderFactory are deleted
• RegistryPropertiesEditionProvider, StandardPropertiesEditionPolicyProvider, StandardPropertiesEditionPolicyProviderFactory and StandardPropertiesEditionProviderFactory are deleted
• PropertiesEditionComponentService and PropertiesEditionPolicyProviderService are deleted

The editing context management have been improved. Associated API changes are :

• IPropertiesEditionContext renamed PropertiesEditingContext
• DomainPropertiesEditionContext, EObjectPropertiesEditionContext and EReferencePropertiesEditionContext implements this interface
• TypedEReferencePropertiesEditionContext is created as sub-class of EReferencePropertiesEditionContext

Some Obsolete classes have been deleted :

• EMFPropertiesRuntime
• EEFMessageManager