// this code used to be smart about which validator was used at which java-path, and provide only the contexts for that particular
// java-path to the processor; but that doesn't work in SEER*DMS where some edits are persisted but not registered to the engine!
private void updateProcessorsContexts(Map<Long, Map<String, Object>> allContexts) {
        // this code used to be smart about which validator was used at which java-path, and provide only the contexts for that particular
        // java-path to the processor; but that doesn't work in SEER*DMS where some edits are persisted but not registered to the engine!
        for (ValidatingProcessor p : _processors.values())
            p.setContexts(allContexts);
    }
private void updateProcessorsContexts(Map<Long, Map<String, Object>> allContexts) {
// this code used to be smart about which validator was used at which java-path, and provide only the contexts for that particular
// java-path to the processor; but that doesn't work in SEER*DMS where some edits are persisted but not registered to the engine!
for (ValidatingProcessor p : _processors.values())
p.setContexts(allContexts);
private void updateProcessorsContexts(Map<Long, Map<String, Object>> allContexts) {
// this code used to be smart about which validator was used at which java-path, and provide only the contexts for that particular
// java-path to the processor; but that doesn't work in SEER*DMS where some edits are persisted but not registered to the engine!
for (ValidatingProcessor p : _processors.values())
p.setContexts(allContexts);
}
private void updateProcessorsContexts(Map<Long, Map<String, Object>> allContexts) {
// this code used to be smart about which validator was used at which java-path, and provide only the contexts for that particular
// java-path to the processor; but that doesn't work in SEER*DMS where some edits are persisted but not registered to the engine!
for (ValidatingProcessor p : _processors.values())
p.setContexts(allContexts);
}