Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P03
-
Fix Version/s: 4.1, EE-3.3.0.GA_P04
-
Component/s: Framework, Sample Apps
-
Labels:None
-
Environment:ICEfaces EE 3.3
-
Assignee Priority:P1
-
Support Case References:Support Case #13433 - https://icesoft.my.salesforce.com/5007000001DTVru
Description
When setting the mandatoryResourceConfiguration context param in the Showcase demo web.xml, the resource tied to the component is not pre-loaded on the page.
For example when using the following:
<context-param>
<param-name>org.icefaces.mandatoryResourceConfiguration</param-name>
<param-value>fileEntry</param-value>
</context-param>
The fileEntry.js.jsf resource is not in the head tag.
For example when using the following:
<context-param>
<param-name>org.icefaces.mandatoryResourceConfiguration</param-name>
<param-value>fileEntry</param-value>
</context-param>
The fileEntry.js.jsf resource is not in the head tag.
Tested with success the 3.3 maintenance branch. Both ace:slideEntry and ace:dateTimeEntry require "util/ace-components.js" and "util/ace-jquery.js" files which are indeed referenced after navigating to the second page. When using icecore:config tag the mandatory resources are read and enforced only when the page is parsed (unlike the context parameter which is read at application load time).