Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0-Alpha3
-
Component/s: Documentation, ICE-Components
-
Labels:None
-
Environment:N/A
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration
Description
Due to problems like ICE-2016 the <ice:portlet> component was introduced, which works very well and is a good solution.
However, JSF 2.0 will feature new <h:head> and <h:body> tags, which I would assume will have <ice:head> and <ice:body> equivalents when ICEfaces implements compliance with a finalized spec of JSF 2.0.
My feature request, is that the <ice:portlet> tag be deprecated, and that the <ice:head> and <ice:body> be used instead.
If the page was like this:
<ice:head>
...
</ice:head>
<ice:body>
...
</ice:body>
... then in a portlet environment, the ICEfaces ViewHandler would know to traverse the <ice:head> subtree first and attempt to insert it in the Portal head. Then, it would traverse the <ice:body> and include just the contents of that in the portlet. During navigation, ICEfaces D2D would attempt to replace only the _contents_ of the <ice:body> subtree.
However, JSF 2.0 will feature new <h:head> and <h:body> tags, which I would assume will have <ice:head> and <ice:body> equivalents when ICEfaces implements compliance with a finalized spec of JSF 2.0.
My feature request, is that the <ice:portlet> tag be deprecated, and that the <ice:head> and <ice:body> be used instead.
If the page was like this:
<ice:head>
...
</ice:head>
<ice:body>
...
</ice:body>
... then in a portlet environment, the ICEfaces ViewHandler would know to traverse the <ice:head> subtree first and attempt to insert it in the Portal head. Then, it would traverse the <ice:body> and include just the contents of that in the portlet. During navigation, ICEfaces D2D would attempt to replace only the _contents_ of the <ice:body> subtree.
Neil, is this still relevant?