Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Beta1
-
Fix Version/s: 3.2
-
Component/s: Framework, ICE-Components
-
Labels:None
-
Environment:All operating systems, software and platforms
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration
Description
BlockUIOnSubmit parameter in web.xml is extremely useful, but in some scenarios will affect application responsiveness too much.
Therefore it will be better to have the possibility to tell the framework that UI must be blocked only for components that requires UI blocking.
I mean:
by now if I set the BlockUIOnSubmit parameter, all components that perform a submit make the UI become blocked. It will be more fruitful if I can specify for components that performs submits an attribute "performsUIblockingOperation" thus to have UI blocked only where this attribute is true.
Therefore it will be better to have the possibility to tell the framework that UI must be blocked only for components that requires UI blocking.
I mean:
by now if I set the BlockUIOnSubmit parameter, all components that perform a submit make the UI become blocked. It will be more fruitful if I can specify for components that performs submits an attribute "performsUIblockingOperation" thus to have UI blocked only where this attribute is true.
It is not possible anymore to choose UIblock for specific forms.
The component ace:submitMonitor doesn't override the settings of blockUIOnsubmit anymore due to the changes in this bug: ICE-10518. Now the element ace:submitMonitor with the attribute blockUI=@none (Which is specific for every form) will not stop the blockUIOnSubmit setting (Which is specific for every page).
I've added a comment to the issue here: ICE-10518 comment.
I've also created a new issue about this: ICE-11454.