Jump to: navigation, search

Difference between revisions of "EMF/Transaction/New and Noteworthy/Galileo"

(Milestone 2)
(M3)
 
Line 3: Line 3:
 
For more details about the development plan, see the
 
For more details about the development plan, see the
 
[http://www.eclipse.org/projects/project-plan.php?projectid=modeling.emf EMF Galileo draft plan].
 
[http://www.eclipse.org/projects/project-plan.php?projectid=modeling.emf EMF Galileo draft plan].
 +
 +
==Milestone 3==
 +
 +
This milestone was completed on Wednesday, 5 November 2008.
 +
 +
====ResourceUndoContext Policy====
 +
 +
This milestone introduces pluggable policies for determining when an [http://download.eclipse.org/modeling/emf/transaction/javadoc/workspace/1.3.0/org/eclipse/emf/workspace/IWorkspaceCommandStack.html IWorkspaceCommandStack] attaches a [http://download.eclipse.org/modeling/emf/transaction/javadoc/workspace/1.3.0/org/eclipse/emf/workspace/ResourceUndoContext.html ResourceUndoContext] to an [http://help.eclipse.org/help32/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/commands/operations/IUndoableOperation.html IUndoableOperation] indicating that an EMF resource is "affected by" the operation in some way.
 +
 +
Simply override the <tt style="color:DarkGreen">getResourceUndoContextPolicy()</tt> method of your [http://download.eclipse.org/modeling/emf/transaction/javadoc/workspace/1.3.0/org/eclipse/emf/workspace/WorkspaceEditingDomainFactory.html WorkspaceEditingDomainFactory] to return an [http://download.eclipse.org/modeling/emf/transaction/javadoc/workspace/1.3.0/org/eclipse/emf/workspace/IResourceUndoContextPolicy.html IResourceUndoContextPolicy], usually a subclass of [http://download.eclipse.org/modeling/emf/transaction/javadoc/workspace/1.3.0/org/eclipse/emf/workspace/AbstractResourceUndoContextPolicy.html AbstractResourceUndoContextPolicy], which has convenient override hooks for tweaking the default behaviour.
 +
 +
====Other Enhancements====
 +
 +
A complete list of the enhancement requests resolved in this milestone can be found
 +
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=Modeling&product=EMF&component=Transaction&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_severity=enhancement&chfieldfrom=2008-09-25&chfieldto=2008-11-05&chfield=resolution&chfieldvalue=FIXED&cmdtype=doit here].
 +
  
 
==Milestone 2==
 
==Milestone 2==

Latest revision as of 15:27, 9 November 2008

EMF Model Transaction New and Noteworthy items for the 1.3 (Galileo) release.

For more details about the development plan, see the EMF Galileo draft plan.

Milestone 3

This milestone was completed on Wednesday, 5 November 2008.

ResourceUndoContext Policy

This milestone introduces pluggable policies for determining when an IWorkspaceCommandStack attaches a ResourceUndoContext to an IUndoableOperation indicating that an EMF resource is "affected by" the operation in some way.

Simply override the getResourceUndoContextPolicy() method of your WorkspaceEditingDomainFactory to return an IResourceUndoContextPolicy, usually a subclass of AbstractResourceUndoContextPolicy, which has convenient override hooks for tweaking the default behaviour.

Other Enhancements

A complete list of the enhancement requests resolved in this milestone can be found here.


Milestone 2

This milestone was completed on Wednesday, 24 September 2008.

Listener API Enhancements

Some long-awaited, and much-needed, additions were made in the listener APIs in this milestone. First, a ResourceSetListener.Internal interface provides private call-backs to ResourceSetListeners that implement it. This new protocol defines call-backs signalling to a listener when it is attached to or detached from a TransactionalEditingDomain. Naturally, all of the implementations of ResourceSetListener that are provided by the EMF Transaction component implement this new interface.

An entirely new listener API is the TransactionalEditingDomainListener interface. This may be attached by clients via a new TransactionalEditingDomain.Lifecycle optional adapter interface for editing domains. The call-backs signal life-cycle events, primarily in transactions, of the following kinds:

  • pre-notification of the starting of a top-level transaction
  • successful start of a top-level transaction
  • interrupted start of a top-level transaction (thus a non-start)
  • pre-notification of the closing of a top-level transaction
  • successful or failed close of a top-level transaction
  • disposal of the editing domain

Unlike the ResourceSetListener API, these listener events do not carry information about the changes that occurred in the EMF data. They do provide information about the management of transactions that was previously unavailable.

Miscellaneous Enhancements

A couple of enhancements aim to provide greater flexibility to clients by removing API restrictions. These include:

  • enabling the definition of arbitrary notification filtering via a new NotificationFilter.Custom class
  • enabling client control over the re-use of the active transaction by an AbstractEMFOperation. This is especially useful for spontaneous construction and execution of commands by others while they are executing, as is often done by edit-helper commands in the GMF Run-time

Other Enhancements

A complete list of the enhancement requests resolved in this milestone can be found here.