The DisbursementResequencer contains a lot of business rules that should exists as Drools rules in the system. Currently, the resequencer just places messages in ModelContext which eventually get displayed to the user.

As part of this, we also need to simplify the validation logic that is in the resequencer. The logic for validation should be identical to the logic for actual process with the exception that, if validateOnly is true, the system should throw a ForceRollbackException or otherwise mark the current transaction for rollback. After changes, there should be little (maybe no?) code in the model that differentiates validation from actual processessing aside from forcing rollback.

To trigger the rules for disbursements, we probably need a new DisbursementResequenceEvent that captures the resequencing parameters that were passed into the service. We need to look at this a little closer and decide exactly what needs to be in this event.