We've created a test Verifier on our Contact Entity. 2 Fields are evaluated by the code below. We do see the Verifiers being executed but we can't find the VerifierResultCollection anywhere. My guess was that it should be somewhere on the VerifierEngine related to the Entity.

 

Regards,

Paul Sinnema

Diartis AG

 

To explicitly make this call, you can create a property interceptor method that will get executed before any property set:

 

 

This method can be implemented in a Base class, in which case, it will be called for any property set.

 

Or you can implement it such that it only applies to properties on a specific type:

 

        [BeforeSet]
        public void BeforeAnyEmployeeSet(PropertyInterceptorArgs<Employee, Object> args)
        {
            var entityPropertyArgs = args as IEntityPropertySetInterceptorArgs;
            var results = this.VerifierEngine.Execute(entityPropertyArgs.Instance, entityPropertyArgs.EntityProperty.Name, entityPropertyArgs.Value);
        }

 

You can also vary the above such that the Execute is called AfterSet, depending on how your verifier is configured.

 

Review the "Property Interceptor" chapter in the Developer's Guide for more details on how to implement property interceptors.

 

 

Thanks for the reply.

 

I already read about the Excecute() method. I was just wondering if the ErrorCollection could be retrieved somewhere for the Verifiers that are executed automatically by DevForce. I guess that not the case then.

 

I don't see how we can benifit from automatcally executing Verifiers if we can't get the Verifiers Result afterwards. We don't want to throw Exceptions for errors. That would limit the Verifier to 1 check and above all it is a general rule of thumb not to use Exceptions for Functional Errors.

 

In the solution, you propose, a [BeforeSet] is used. Wouldn't this approach fire Verifiers excessively. Changes to fields also fire the (automatic) Verifiers.

 

The Execute() would, of course, be fine at the moment the data is being saved. We would get all the Verifiers executed and return their result(s).

 

If we would like to use the [BeforeSet] approach, is there a way to disable the automatic verifiers of IdeaBlade?

 

Regard,

Paul Sinnema

Diartis AG

 

Thanks for sticking with me. We probably will need both. The verifiers are automatically fired on a per-property basis. Before save we will need to verify everything. The latter is no problem because we can use the Execute() which returns the ErrorCollection to us. On a per-property basis is the issue here. Each time a property is changed, attached Verifiers are fired. The errors that come from these Verifiers also need to be displayed (and adorned on the field). We know of the automatic WPF Adorners which are shown automatically when an exception is thrown. This would however limit the verifiers. Every time an exception is thrown the other Verifiers will no longer be fired. And as I said earlier. A rule of thumb is not to use Exceptions for functional errors.

 

Regards,

Paul Sinnema

Diartis AG

 

Have you looked at the WPF code sample found in "Learning Resources\060_Validation\Code Samples\200WC WPF"? It shows you how to set an attribute on the binding so that the UI can handle the errors thrown by the VerifierEngine.

 

The way it works is "attributed verifiers" are automatically generated by the Object Mapper (for String and required types) to enforce database constraints. You can see the attributed verifiers in the Designer file generated by the Object Mapper. Additional verifiers can be implemented in the Developer class.

 

You would then need to set an attribute on the binding in the XAML so that the result of a verification exception thrown by a property setter will display (by default) the control in which the data item was modified encircled by a red box with an asterisk placed next to it. Hovering the mouse cursor over the asterisk will display the verification error message.