| Live vs Batch validation [message #1513587] |
Tue, 16 December 2014 12:15  |
Eclipse User |
|
|
|
Hi again,
Apparently Live validation does not create an entry in the Eclipse Problems view. Is there any way to convert these Live validation errors so that they are persisted the same way as Batch errors, or do I need to define two different constraints, one for mode="Live" and one for mode="Batch"?
Thanks!
Bob
|
|
|
| Re: Live vs Batch validation [message #1513765 is a reply to message #1513587] |
Tue, 16 December 2014 15:39  |
| Eclipse User |
|
|
|
Hi, Bob,
Live validation rules are run in batch mode, so when you perform a
batch validation, those rules should also be producing problem markers.
If you need rules to produce problem markers when they are run in live
mode, then you may be able to implement a validation listener that
creates the problem markers, but then you have the problem of how to
detect when markers are stale and need to be deleted. The live
validation was originally designed primarily to support the EMF
Transactions, so that rules could trigger transaction rollback. In
such case, problem markers wouldn't make sense because the changes
having been reverted means that the model does not enter an ill-formed
state and there's nothing to mark up.
HTH,
Christian
On 2014-12-16 17:15:45 +0000, Robert Brodt said:
> Hi again,
>
> Apparently Live validation does not create an entry in the Eclipse
> Problems view. Is there any way to convert these Live validation errors
> so that they are persisted the same way as Batch errors, or do I need
> to define two different constraints, one for mode="Live" and one for
> mode="Batch"?
>
> Thanks!
> Bob
|
|
|
|
Powered by
FUDForum. Page generated in 0.05013 seconds
Home