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
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.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
During development of the PortletFaces Bridge, I had some communication with Ted and Deryk on this matter. You'll have to double check with them, but I believe the overarching goal is to not require portlet-specific tags like ice:portlet in ICEfaces 2.0, so that you can more easily take an ICEfaces webapp and slide it into a portlet container for deployment as a portlet.
In ICEfaces 1.8, we required the use of a custom ice:portlet tag to uniquely identify that area of the page that contained a JSF/ICEfaces view. With JSF 2/ICEfaces 2/PortletFaces bridge, this is no longer necessary but for backwards compatibility. Rather than develop a version of the tag that's harmless, we are documenting that it should simply be removed as it is unsupported going forward.
Documented and closing as Won't Fix.
Neil, is this still relevant?