Bug 250136 [KeyBindings] Conflicts should be accessible through API
See org.eclipse.jface.bindings.BindingManager.setActiveBindings(Map, Map, Map, Map) We currently use org.eclipse.jface.internal.InternalPolicy.currentConflicts to transport the conflicts around, it should be available through the BindingManager (and probably the IBindingService API) PW
bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/BindingManager.java
boolean activeSchemeChanged = false;
			if (schemeIdAdded) {
				definedHandleObjects.add(scheme);
			} else {
				definedHandleObjects.remove(scheme);
				if (activeScheme == scheme) {
					activeScheme = null;
					activeSchemeIds = null;
					activeSchemeChanged = true;
					
					clearSolution();
				}
			}
			if (isListenerAttached()) {
				fireBindingManagerChanged(new BindingManagerEvent(this, false,
						null, activeSchemeChanged, scheme, schemeIdAdded,
						false, false));
			}
		}
	}
	/**
	 * Sets the active bindings and the prefix table. This ensures that the two
	 * values change at the same time, and that any listeners are notified
	 * appropriately.
	 * 
	 * @param activeBindings
	 *            This is a map of triggers ( <code>TriggerSequence</code>)
	 *            to bindings (<code>Binding</code>). This value will only
	 *            be <code>null</code> if the active bindings have not yet
	 *            been computed. Otherwise, this value may be empty.