Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Beta2
-
Component/s: Framework, ICE-Components
-
Labels:None
-
Environment:icefaces2, ace
Description
With AJAX, there are problems when modifying the <head>, that necessitate techniques to avoid doing so. With ICE-6047, we solved an issue where a postback could cause an ice:gmap component to become rendered, and in doing so, modify the head, as its javascript resources become added to the head. The solution for that was to recognise when the ice:gmap component was in a JAR in the WAR, and thus had the potential for being in the application, then, via a config param, allow for its resources to always be in the head. This was done by annotating the GMapRenderer, so it's self-describing, and there's no central list of components being reflectively sought.
Now, consider the ace components, which each have many resource dependencies, which would modify the head if the components were dynamically ui:included, or their rendered property were toggled. So, we want to annotate them so that when the ACE JAR is in the WAR, their @ResourceDependency annotations will always be processed, whether they're in the view yet or not.
Now, consider the ace components, which each have many resource dependencies, which would modify the head if the components were dynamically ui:included, or their rendered property were toggled. So, we want to annotate them so that when the ACE JAR is in the WAR, their @ResourceDependency annotations will always be processed, whether they're in the view yet or not.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion