ThemeDisplay themeDisplay = (ThemeDisplay) ((RenderRequest) (facesContext.getExternalContext().getRequest())).getAttribute(WebKeys.THEME_DISPLAY) ĭo you know why portletFacesUtil is null? In order to get it workin with ICEfaces i had to edit the InputHTMLRenderer.java because However, these portlets also share a single set of configuration files (web.xml, portlet.xml, etc.) so it's important to understand the implications. I managed to get the inputHTML component to work. If multiple ICEfaces portlets are bundled together in a single archive, they gain the ability to share some common state and, using Ajax Push, benefit from a form of inter-portlet communication. Fore more info, download the the Liferay Plugins SDK documentation. The sources are meant to be extracted into the "plugins" folder of the Liferay Plugins SDK. I confirm that this is a correct solution - adding mime types to web.xml.
#Web.xml icefaces code
• Source code for Demo #4: ICEfaces IPC Ajax Push Portlet (Liferay Plugins SDK ZIP, 4.7 MB) putting this into web.xml fixes the issue:The first two steps are fairly straight forward but the last two steps need to be described in detail. It should point to the properties file that contains the relevant JMS information for the platform being used. Add the FaceletViewHandler to the faces-config.xml file. This parameter is used in the web.xml file of the AHS server as well as the web.xml of any ICEfaces application that is defined to use AHS. Add the Facelet init parameter to the web.xml file. Copy the icefaces-facelets.jar into your WEB-INF/lib directory.
#Web.xml icefaces archive
Note: An archive of the webinar is now available on ICEfaces.
Please wait for the web application to start.
.ORIGINAL POST FOLLOWS: September 30, 2008 Im trying to run small application (app using IceFaces 1.8.2). I would encourage you to try out the ICEfaces 2 versions of these portlets here: This blog post refers to an old version of ICEfaces (1.8).