Constraints are evaluated immediately before and after write operations are performed. Server-side constraints are evaluated in two phases: the first phase determines if the proposed add, delete, or modification is acceptable according to the constraint. If one or more constraints fails, the write write operation is refused, and the client will receive an OperationRejectedException exception. The second phase is invoked once the add, delete, or modification request has been allowed and any changes applied. The second phase gives the constraint handler a chance to register listener call-backs if required.
A server constraint handler must override at least one of the provided methods. @see org.nasutekds.server.admin.Constraint
| |