The current behaviour of ICEfaces in a portal environment is for the initial request to go through the portal container, generating a RenderRequest. The RenderRequest is handled by our own MainPortlet which routes it to the MainServlet and the rest of the ICEfaces framework. In a portal environment, typical client interaction with a portlet would also go through the portal container, generating an ActionRequest. Currently, ICEfaces does not do this. All client interaction is done via Ajax and the resulting requests go straight to our own framework servlets, bypassing the portal container. This has a number of consequences for the developer (some of which are documented in other JIRA cases):

- Session last accessed time is not updated properly
- ActionRequest/ActionResponse APIs are not available to the portlet developer preventing programmatic control of things like portlet modes (view, edit, help, etc) and window states (minimized, maximized, etc)