Since the default is no longer null, which was used originally to indicate that all resources should be pre-loaded, there is now no way to set the mandatoryResourceConfiguration to a value that will engage the fully-automated resource loading behaviour, if desired.

We need to add support for an additional value for mandatoryResourceConfiguration, "all" or maybe "auto", which would re-instate the automatic detection and loading of component resources via class path detection.

An additional mandatoryResourceConfiguration parameter value string is now supported - 'all'. When 'all' is specified, ICEfaces will preload all component resources in the initial page GET for all components on the class path. This provides an easy way to ensure all component resources are present when needed, at the significant expense of loading JS resource for components that may not even be used on the page.

The 'all' behaviour matches the previous default mandatoryResource behaviour.

A regression has been found using svn rvn# 25909 in that even though the default value is still reported as being "none" in the startup log for the mandatoryResource setting, it is now loading all ACE JS resources into the head during the initial page load, just as if the default as still null (or the newer "all" setting). This is incorrect, by default the "none" setting should not be loading any ACE resources for components that aren't already on the page during the GET.

To illustrate this issue, run the auction sample and add the icefaces-ace.jar to it and you'll see all the ace resources being loaded into the browser, even though none of them are used in the application.

Mircea, looks like you forgot to change BridgeSetup.java to only use/ load the entire mandatoryResource class list from the jar if mandatoryResourceConfig != "none".

Fix checked in and tested with both icecore:config and web.xml variants. Recommend additional testing in customer application.