Hello Ken,
The blockUIOnSubmit configuration is a global (or per page) configuration and is not meant to be mixed with the ace:submitMonitor component.
Why?
I still don't understand why this is done, as it has been a feature. Now it is only possible to do blockUIOnSubmit for the whole application OR specify it to every component or page (a lot of redundant work!). But what you cannot do, is to set a blockUIOnSubmit for the whole application and then specify for a specific use case something else.
This is your own comment: "There should be an order of precedence such that a more specific monitor will override a more general one, in cases where more than one monitor might be in effect for the same submit." [Comment on ICE-7740]
Isn't the component ace:submitMonitor more specific than the global setting blockUIOnSubmit?
In my scenario, I have over 500 forms on over 300 pages. I want all of the forms to be such that you should block the UI when you do submit something. That is why the setting org.icefaces.blockUIOnSubmit is really good here. But now I have one form that I shouldn't block the UI when submitted. So the only way for me to make it possible is to refactor the whole application?
If there isn't a specific reason why the components ace:submitMonitor attribute blockUI shouldn't override the global setting, then it would be a good idea to fix this.
P.S. What did you want to say with the icecore:config link?
See the <icecore:config> Wiki topic for details: http://www.icesoft.org/wiki/display/ICE/config
Attached test case that shows this issue. Note, the icefaces, ace, and compat jars need to be added into the war for it to run.
Steps: