Difference between revisions of "EMF/MQ, MT, and VF 1.1/New and Noteworthy"
m |
|||
| Line 15: | Line 15: | ||
class make it easy to create multiple results and combine them into a single multi-status | class make it easy to create multiple results and combine them into a single multi-status | ||
(which also is an | (which also is an | ||
| − | [http://download.eclipse.org/technology/emft/validation/javadoc/1.1.0/org/eclipse/emf/validation/model/IConstraintStatus IConstraintStatus]. | + | [http://download.eclipse.org/technology/emft/validation/javadoc/1.1.0/org/eclipse/emf/validation/model/IConstraintStatus.html IConstraintStatus]. |
[[Image:EMFT-val-multistatus.png|frame|Multiple results from one constraint]] | [[Image:EMFT-val-multistatus.png|frame|Multiple results from one constraint]] | ||
| Line 31: | Line 31: | ||
For other bug fixes, see the | For other bug fixes, see the | ||
| − | [http://www.eclipse.org/emft/news/relnotes.php?project=query&version=1.1M4 Query], [http://www.eclipse.org/emft/news/relnotes.php?project=transaction&version=1.1M4 Transaction], | + | [http://www.eclipse.org/modeling/emft/news/relnotes.php?project=query&version=1.1M4 Query], [http://www.eclipse.org/modeling/emft/news/relnotes.php?project=transaction&version=1.1M4 Transaction], |
| − | and [http://www.eclipse.org/emft/news/relnotes.php?project=validation&version=1.1M4 Validation] 1.1 M4 release notes. | + | and [http://www.eclipse.org/modeling/emft/news/relnotes.php?project=validation&version=1.1M4 Validation] 1.1 M4 release notes. |
Revision as of 15:45, 22 December 2006
EMFT Query, Transaction, and Validation Release 1.1 New and Noteworthy Items.
For more details about the milestone-by-milestone development plan, see the 1.1 draft plan.
Back to EMFT.
Contents
1.1 M4
Multiple Results from one Validation Constraint
A single constraint can now report multiple results, for different but related problems in one or more model elements. New utilities on the ConstraintStatus class make it easy to create multiple results and combine them into a single multi-status (which also is an IConstraintStatus.
Removing Resources from Transactional Editing Domains
Resources and model elements can now be safely removed from the grip of a transactional editing domain. New utilities on the TransactionUtil class allow a resource or object that has already been detached from the editing domain's resource set to be released from the "transaction protocol." This is particularly useful when the resource/object in question is to be moved into another resource set context, which may or may not be controlled by a transactional editing domain.
Other Bug Fixes
For other bug fixes, see the Query, Transaction, and Validation 1.1 M4 release notes.