Bug 177643 - TransactionalEditingDomain's TransactionValidator should be configurable
Summary: TransactionalEditingDomain's TransactionValidator should be configurable
Status: VERIFIED FIXED
Alias: None
Product: EMF Services
Classification: Modeling
Component: Transaction (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P2 enhancement
Target Milestone: ---   Edit
Assignee: David Cummings CLA
QA Contact:
URL:
Whiteboard:
Keywords: api, contributed
Depends on:
Blocks:
 
Reported: 2007-03-15 16:03 EDT by Christian Damus CLA
Modified: 2017-02-24 15:10 EST (History)
0 users

See Also:

Attachments
Proposed patch (16.03 KB, patch)
2007-03-22 14:45 EDT, David Cummings CLA 		wayne.beaton: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Damus CLA 2007-03-15 16:03:04 EDT 
Currently there is no way to configure the transaction validator associated with a transactional editing domain.  In the TransactionalEditingDomainImpl, the validator defaults to using a live validator to validate the transaction.  If the user wishes to configure that validator (perhaps to set filters or report successes), they have no mechanism to do so.

TransactionalEditingDomain should provide a mechanism to configure its transaction validator.
Comment 1 David Cummings CLA 2007-03-22 14:45:36 EDT 
Created attachment 61723 [details]
Proposed patch
Comment 2 Christian Damus CLA 2007-03-22 15:13:49 EDT 
Commited the patch, with the following changes:

  - made the ValidatorFactory interface a nested interface in TransactionValidator
    (as TransactionValidator.Factory) to match the usual EMF pattern
Comment 3 Nick Boldt CLA 2008-01-28 16:35:31 EST 
Move to verified as per bug 206558.