Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-2.0.0.Alpha1
-
Fix Version/s: EE-2.0.0.Beta1
-
Component/s: Facelet Components
-
Labels:None
-
Environment:JSF 2.1
Description
Similar to IPCk-203 This bug is meant to capture a perforamnce issue when rendering out the editable data table. Clicking on the demo/component quickly seems to make the application unresponsive. There are no rendering exceptions.
A closer look needs to be done to see if the renderer can be optimized and or there is some other component or demo issue.
A closer look needs to be done to see if the renderer can be optimized and or there is some other component or demo issue.
Issue Links
- blocks
-
IPCK-204
Rich Data Grid peformance issues.
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Performance issues were likely noticed after singleSubmit was applied application wide to the composite-comps-showcase.
This component was not designed to have partialSubmit/singleSubmit enabled on all the child tags.
Show
Brad Kroeger
added a comment - Performance issues were likely noticed after singleSubmit was applied application wide to the composite-comps-showcase.
This component was not designed to have partialSubmit/singleSubmit enabled on all the child tags.
Resolving this issue as the showcase has been modified to apply singleSubmit on a demo by demo basis and is no longer applying singleSubmit to the editableTable.
Show
Brad Kroeger
added a comment - Resolving this issue as the showcase has been modified to apply singleSubmit on a demo by demo basis and is no longer applying singleSubmit to the editableTable.
It seems that some of the performance issues might be related to the general use of the icecore:singleSubmit tag in the demo application. This is causing any visited input fields, such as data entry fields in editable datable, to do a singleSubmit onblur. This adds numerous extra submits and lifecycles and is not necessary for this demo as it's written to valid, etc. on "save" by clicking the save button.
Changes should be made to the structure of the sample app. to avoid using singleSubmit in a blanket fashion, so that each demo can apply it as required.