On the surface this might sound like a rare case, but using a JSF EL expression to control conditional rendering (when used in conjunction with D2D) makes for a way to avoid navigation-rules altogether, and keep things going in an ICEfaces extended-request scope for longer periods of time. This is strategy I am using extensively in a production application I built with ICEfaces.

To reproduce this problem:

1. Download and Install the Liferay 4.4.2 + Tomcat 6.0.16 bundle
2. Run the bundle, which will create a $HOME/liferay/deploy folder
3. Download the test-icefaces-render-toggle-portlet.war attached to this ticket and copy to $HOME/liferay/deploy
5. Start IE7
6. Login as test@liferay.com with password test
7. Position the mouse over the "Welcome" dock in the upper right hand corner
8. Navigate to "My Places > My Community > Private Pages"
9. Add a page named "Render Toggle"
10. Under the "Add Content" menu, expand the "Test" category
11. Add the "Test ICEfaces Render Toggle" portlet

Click on the "Show Tabs" button

If the bug still exists, then the <ice:tabbedPanel /> will not appear.

if the bug is fixed, then the <ice:tabbedPanel /> will indeed appear.

To prove that it is the presence of the <ice:richInputText /> that is causing the problem, you can simply delete the <ice:richInputText /> from the view.xhtml page after hot deployment, and try it again. When I deleted it, the "Show Tabs" button started working.