![]() setCompressDom public void setCompressDom(java.lang.The default value for the parameter used to enable/disable the coalescing is false. This way the application can be configured to deterministically coalesce the resources that are known to be used most of the time. MandatoryResourceConfiguration can be used to pre-define the resources that are needed right away (on session start). ![]() During the regular JSF component lifecycle, events are handled, components are created, and an HTML DOM rendering of the page is created on the server. This behaviour avoids the continuous reloading of the coalesced resource, every time the set of required resources has changed. The ICEfaces framework builds on the JSF component model to provide a server-centric way of creating rich Internet applications. The feature uses the Resource dependencies metadata to coalesce the resources in the correct order.Īny request issued after the first GET request (for the user session) that changes the type and number of required resources will trigger only the loading of the newly required resources. I double checked the code in my JSF pages, it seems no problem for the same build EAR file I put into JBoss and it works well. By reducing the numbers of requests made by the browser the page load time will improve significantly. The coalescing is applied to Javascript and CSS resources resulting into two separate resources, one for the coalesced Javascript and the other for the coalesced CSS. IIRC, the only way to prevent the modal popup is with the OutConnStat component. Setting to true indicates to the ICEfaces core framework that the resources required by the rendered components are to be coalesced. The problem is, when the connection times out no buttons are clickable anymore, what Im trying with my Javascript code is the auto-recover the lost connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |