• http://www.vogella.com/articles/EclipseEMFPersistence/article.html
  
• http://www.vogella.com/articles/EclipseEMFNotification/article.html
  

	private EContentAdapter eContentAdapter = new EContentAdapter() {

		/**
		 * {@inheritDoc}
		 */
		@Override
		public void notifyChanged(
				org.eclipse.emf.common.notify.Notification notification) {
			super.notifyChanged(notification);
			System.out
					.println("Notfication received from the data model. Data model has changed!!!");

		};

	};

	/**
	 * {@inheritDoc}
	 */
	@Override
	public void selectionChanged(IWorkbenchPart part, ISelection selection) {
		if (selection instanceof IStructuredSelection) {
			Object obj = ((IStructuredSelection) selection).getFirstElement();
			if (obj != null) {
				IFile emfResourceFile = (IFile) Platform.getAdapterManager()
						.getAdapter(obj, IFile.class);
				if (emfResourceFile != null) {

					ResourceSet resourceSet = new ResourceSetImpl();
					Resource resource = resourceSet.getResource(
							URI.createURI(emfResourceFile.getFullPath()
									.toString()), true);
					EObject eObject = resource.getContents().get(0);
					eObject.eAdapters().add(eContentAdapter);
					System.out.println(eObject);
				}
			}
		}

	};

Stefan,

Comments below.

On 28/12/2012 12:31 PM, Stefan Weiser wrote:
> Hello Ed Merks,
> thank you for your hints.
>
> Now I can identify changes made by code but not changes in a running
> instance of Eclipse.
>
> Adding it to the ResourceSet doesn't really solve the problem I've
> got. The ResourceSet seems to be a snapshot from the selected part and
> doesn't recognize further changes afterwards.
I have no idea what you're doing in the code you showed. Yes of course
it's just local objects that will be garbage collected unless you keep
some reference to it...
> Or I don't use it in a correct way.
> So what can I do, if I'd like to notify changes I'm doing on the
> models in an editor in an Eclipse-instance.
In the generated editor, you can add such a content adapter to the
editing domain's resource set, e.g., by specializing the createModel method.
> Snapshots of the models doesn't really help me for my task. I hope my
> problem is understandable.

• An editor-specific implementation, which identifies changes on models.
  
• Implementing a ResourceChangeListener on the workspace, which is not EMF specific.
  

Stefan,

Listening to the workspace is the only way to know about changes that
are actually saved. You can't in general know about changes happening
internal to editors, and each editor generally maintains it's own local
instances. Generated EMF editors do implement IEditingDomainProvider
which provides access to the editing domain and hence the resource set.