Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.6.1
-
Component/s: ICE-Components
-
Labels:None
-
Environment:Portal
Description
In D2D rendering, we frequently climb the DOM tree looking for a parent container to consolidate a number of changes. In JSF, this parent container is typically a sub-class of UINamingContainer. Most of the time, this duty is handled by using <ice:form>. However, particularly in portlet environments, it would be useful to have a NamingContainer component that is simply a container (as opposed to something like a form which has lots of other complex behaviour) that can be used to wrap the entire contents of the portlet. The component could be very generic so that it can be used in many different scenarios (i.e. non-portlet) or it could be specifically for portlets only. Or there could be both: a generic container with a more specific portlet container. Other than taking the basic JSF attributes (like id, styleClass, etc) it doesn't need to have any special behaviour other then inheriting from UINamingContainer.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Assigning to Yip (since he did all the hard work) and then marking as fixed. I've successfully used this in a couple of test portlets now and it appears to have helped with
ICE-2016where navigation works much better now. I changed the logic in the component so that the getClientID now uses the portlet namespace which allowed us to get rid of the NamespacingViewRoot.