while working on my connector, I found a bug, it is a quite obvious thing:
When AD is requested to delete a folder, it will recursively try to delete its children first. While doing this, it will call the "execute()" method of the registered "GetChildrenHandler".
But, otherwise than in all other occasions, it does not provide an IProgressMonitor instance, but provides just null.
So, my GetChildrenHandler::execute() implementation must check whether monitor is null, before use.
That conflicts with the expected agreement, and breaks code. If the IProgressMonitor could be null in any handler call, then I would have to lard my code with many "if( monitor!=null ) .." cases. That does not sound much sensible.