Latest posts for the topic "Liferay Portal-ICEfaces Integration"

Liferay Portal-ICEfaces Integration

philip.breau — GMT

Hi everybody, There's been a lot of interest shown on integration between ICEfaces and the Liferay portal, so this is a thread to start a discussion on this topic. If you have want to use Liferay with ICEfaces, and have any particular integration concerns/stories, issues about requirements, etc, feel free to add them here. In the meantime here's a list of some of the other threads concerning Liferay: IceFaces + Seam + Portlet + Facelets Anybody want to use Portlets with ICEfaces? any issues with JSF Components and JSF Portlets ICEfaces on JSR-168 portlet with Seam + facelets Failed to execute JSP lifecycle when portlet is called Thanks, Philip

Re:Liferay Portal-ICEfaces Integration

kunzem — GMT

Nice step to complete the wall :)

Liferay Portal-ICEfaces Integration

erron — GMT

Since I use Liferay, I wouldn't mind an integration. However, I would suggest that the integration be more at the JSR-168 spec level rather than the portal itself, so that a user could deploy to whatever portal environment desired.

Re:Liferay Portal-ICEfaces Integration

redly2001 — GMT

i'm just trying to get it to work and it looks not bad until jet. my setup: liferay 4.2.0 (tomcat bundle) MySql 5.0.27 IcEfaces 1.5.1 TopLink v2.25b for portlet persistence Facelets as viewHandler My testapp is an aggregation and customization of the seam+ icefaces+portlet sample, some parts of the icefaces webmail sample und a lot of other tutorials und samples on the net (which all cannot be mentioned) In Firefox my portlet works - with some js errors on the javascript console however. In IE i can get the same state if i disable the liferay ajax functions (based on prototype framework). The js error on load in IE: Line: 1668 Char: 1 Error: Object doesn't support this property or method Code: 0 and if i try to click a button or commandlink i get an error like: object "connection" unassigned. i think there is a conflict between the icefaces and liferay ajax functionality - will continue to examine these problems. Any kind of help would be highly appreciated! If there is some interest in my testapp i will provide it as a zip file in the forum. thanks, michael

Re:Liferay Portal-ICEfaces Integration

redly2001 — GMT

ok - now it works for me :-) i was build a new icefaces-d2d.js file without prototype framework because it is already there in liferay.then i commented out the following lines of code: /* if(window.Event){ document.captureEvents(Event.KEYDOWN); document.captureEvents(Event.MOUSEDOWN); } */ as far as i know this code is only needed for netscape 4 browsers. i will provide a little sample portlet the next days, when i have some spare time.

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Philip, The company I work for uses Liferay 4.1.0, but will upgrade to Liferay 4.2.1 once it is released. We have many JSF portlets developed and deployed with Liferay. However, none of the portlets make use of AJAX, so I am eager to rewrite some/all of them using IceFaces components. My observation is that IceFaces+SEAM is the future, so I am eager to begin testing this combo within Liferay as soon as you solidify your JSR-168 portlet support in your SVN snapshots. Also, I ran across this JSR-286 (Portlet 2.0) presentation the other day: http://www.ja-sig.org/wiki/download/attachments/19378/JSR286_Preview.pdf?version=1 Recommend that you all give the presentation a look-see, as Liferay is on the JSR-286 expert panel, and as slide#28 indicates, AJAX is still "forthcoming" in JSR-286. Frankly, I am concerned that the JSR-286 expert group may not be communicating closely with the JSF 2.0 folks (not sure if that JSR has been filed yet). I think that the IceFaces partial-submit and Direct-To-DOM features are candidates for standardization within JSF 2.0, but there may be an opportunity here for the JSF 2.0 folks to communicate better with the JSR-286 folks regarding AJAX/JSF portlets. Finally, I thought it worth mentioning that Liferay 4.2.x introduced a new "parallel portlet rendering engine", which enables portlets to render themselves individually (I think using AJAX). Very cool stuff indeed. Best Regards, Neil

Re:Liferay Portal-ICEfaces Integration

redly2001 — GMT

here is the promissed little sample portlet for the liferay portal. the portlet is based on the seam+icefaces+portlet sample provided here in the forum (hopefully it was ok to use it) it was tested on a liferay 4.2.0 prof. (the tomcat bundle) the war file is an eclipse export with source included and can be autodeployed inside liferay. after adding an instance on a page, a page reload is required to initialze the portlet correctly. have fun!! greetings michael

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Michael, Thanks so much for the sample WAR. I dropped it into my Liferay 4.2.0 hot deploy folder, and these are my results: 1. After copying it to my hot deploy folder and starting Liferay/tomcat, I had to shutdown Tomcat and restart in order for all the CSS stuff to look right. But that's no biggie. 2. I can run the portlet successfully if I download a fresh copy of Liferay 4.2.0, but if I try it with the Liferay "Chat" portlet, I get I get a "permission denied" javascript error when the page loads in IE7. In Firefox 2.0, the error is more precise: "uncaught exception: Permission denied to get property Location.hash" You see, the Liferay "Chat" portlet is a new AJAX creature, and requires the following modifications to the portal-ext.properties file: jabber.xmpp.server.enabled=true reverse.ajax.enabled=true I think it might be the "reverse.ajax.enabled" property that causes the problem. Regardless, great stuff Michael! I had posted a link to this article at the Liferay Message Board, and Michael Young asked if I could create a sample portlet. Seconds later, YOU posted this demo portlet! How about that. So thanks for saving us all a lot of time. Best Regards, Neil

Re:Liferay Portal-ICEfaces Integration

redly2001 — GMT

neil many thanks for testing my little portlet and even more for your kindly ratings. i have tried to reproduce your problem but i was not able to setup the chat portlet. i have done the properties configuration and added a chat instance to a page with my hello world portlet but this does not trigger the problem :-( so i think i have to wait for the chat wiki or presentation to get the jabber things to work. then i can take a further look on that problems. i will subscribe to the liferay forum where we can treat this theme any further if you like. best regards michael

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Michael, Sounds great. BTW, I have a post at the Liferay message boards here: http://www.liferay.com/web/guest/devzone/forums/message_boards/message/24856 Thanks again, Neil

Re:Liferay Portal-ICEfaces Integration

icheung — GMT

after adding an instance on a page, a page reload is required to initialze the portlet correctly.

Michael, Set ajaxable to false in liferay-portlet.xml false Referenced here http://www.liferay.com/dtd/liferay-portlet-app_4_2_0.dtd Also, we have a chat wiki up with instructions to setup. http://wiki.liferay.com/index.php/Chat_Portlet Cheers, ivan

Re:Liferay Portal-ICEfaces Integration

redly2001 — GMT

Ivan, The wiki i had already found and followed it but can't get the chat portlet to work. Maybe i have a typo or something like that, will give it another try as soon as possible. Many thanks for your support! Cheers, michael

Re:Liferay Portal-ICEfaces Integration

igor_b — GMT

Hi, I have deployed HelloWorld portlet to Liferay 4.2.1 portal. It works great. I tried to play with effects adding two commandButtons that invoke Appear and Fade effects on panelGrid. After deployment, previous funcionality of portlet stayed but there is no any sign of effects. Do anybody succeded to applay effects in portlets? Is there any additional steps to do except those written in Developers guide. Thank you!

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

I have tried to get effects to work within Liferay 4.2.1 as well. But I ran into JavaScript problems.

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

NOTE: THIS POST CONTAINS SOURCE CODE FIXES. SEE THE NEXT POST FOR A HELLOWORLD TYPE OF .WAR. I have been working with ICEfaces-1.5.3 and Liferay-4.2.1 now for a couple of weeks. All testing has been done within Tomcat-5.5.17 and jdk1.5.0_09. Note that I had to put the com.icesoft.faces.delegateNonIface=true context-param in my web.xml file so that I could run ICEfaces portlets alongside my legacy JSF portlets within the same Liferay .WAR deployment. Attached to this post is all the ICEfaces-1.5.3 source code that I modified to get things working well within Liferay. If you grep through the files for "neil.griffin" then you will find many comments were I try to explain my fixes. Here is a summary of them: - Added support for the EDIT/HELP modes of the [url=http://portals.apache.org/bridges/multiproject/portals-bridges-jsf/index.html]Apache-JSF-Portlet-Bridge[url] - Added suport for the VIEW/EDIT/HELP modes of the Sun JSF Portlet Bridge and didn't want to change. - Fixed the D2D View Handler's getResourceURL() method, so that in portlet environments, the URLs will always include the webapp-context-base-path. I also fixed several components so that they would call the getResourceURL() method to construct URLs for images. - Fixed the tag so that CSS files with a leading "/" character would prepend the webapp-context-base-path. - Fixed several problems with the component: 1. Rendered was not transparent, and not letting the Liferay theme show through the background 2. Rendered had hard-coded width/height which was redundant with the syntax. 3. Page generated from the FileUploadServlet that appears within the was not getting the webapp-context-path prepended to CSS filenames 3. Rendered had wide margins, which needed to be eliminated. I got the margins almost all gone, but the rendered element still is indented about 3 pixes too much. 4. A reference to the InputFile object was being stored in the session as an attribute, and then picked up again by the FileUploadServlet and DiskFileUpload classes. When running within Liferay, the session attribute name gets changed, so I had to fix the code to find the session attribute name that Liferay generates. - The XP theme (xp.css) had some global "body" styles and some other hard-coded colors that were incompatible with Liferay themes. I have commented them out, and have suggested to ICEsoft that these global settings be placed in a separate CSS file (like xp-global.css). I did not mess with the Royale theme. Now, as a more permanent solution, I recommended to ICEsoft that the component be given a new "renderForPortlet" attribute, so that the following could be done, fixing the problem so that JSPX pages can run in both Servlet and Portlet environments without change: Enjoy, Neil

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

This post contains a "Hello World" type of .WAR for use with Liferay-4.2.1. NOTE#1: THE WEB-INF/lib FOLDER CONTAINS MY PATCHED, BINARY VERSIONS OF THE FOLLOWING .JARs: - icefaces-comps.jar - just-ice.jar NOTE#2: YOU HAVE TO EXTRACT THE WAR, ADD SOME JAR FILES TO THE WEB-INF/lib FOLDER, AND RE-JAR-UP THE WAR BEFORE YOU CAN DEPLOY IT TO LIFERAY. SEE THE "README-NEED-MORE-JARS.TXT" FILE IN THE WEB-INF/lib FOLDER FOR MORE INFO. The attached WAR contains two Portlets: - ICEHelloWorldSunJSFPortletBridge - SunHelloWorldSunJSFPortletBridge As the name indicates, they are designed to work with the SUN (Not the Apache) JSF-Portlet Bridge, and the Sun JSF Reference Implementation (not MyFaces). It is designed to show that ICEfaces portlets can live in the same portlet-war-webapp (and even render on the same page as) legacy/standard JSF portlets (of which I have many). Note that the com.icesoft.faces.delegateNonIface=true context-param must appear in the WEB-INF/web.xml file to enable this cohabitation. Each portlet works with the VIEW/EDIT/HELP modes supported by the Sun JSF-Portlet Bridge. Due to a lack of time, I wasn't prepared to include the following JARs in this WEB-INF/lib folder. I am very concerned about licensing, and I didn't have time to investigate all the open source distributable licenses for these JARs. So instead, I leave it to the reader to track down these JARs and put them in this WEB-INF/lib folder. Once that's done, you can zip up the ICEHelloWorldSunJSFPortletBridge/ folder into a .WAR file, and drop it in the Liferay hot deploy folder for deployment to Liferay. The following JARs ship with ICEfaces-1.5.3, and so you can get them from the binary distribution: - backport-util-concurrent.jar - commons-beanutils.jar - commons-collections.jar - commons-digester.jar - commons-discovery.jar - commons-el.jar - commons-fileupload.jar - commons-lang-2.1.jar - commons-logging-api.jar - commons-logging.jar - el-api.jar - jsf-api.jar - jsf-impl.jar - jstl.jar - krysalis-jCharts-1.0.0-alpha-1.jar - xml-apis.jar The following Log4J file can be downloaded from: http://logging.apache.org/log4j/docs/index.html - log4j-1.2.14.jar And the following Sun-JSF-Portlet-Bridge file ships with Java Studio Creator 2, which can be found here: http://developers.sun.com/prodtech/javatools/jscreator/downloads/index.jsp - jsf-portlet.jar Now, the one that I am using is 53,989 bytes in size. I do have a concern that the latest release of Java Studio Creator 2 is shipping a jsf-portlet.jar that is built for use with the Sun GlassFish server, and JSF 1.2. If this is the case, then the latest jsf-portlet.jar that ships with Java Studio Creator 2 might not be the right one, or might not work. Enjoy, Neil Griffin Triton Services, Inc.

Re:Liferay Portal-ICEfaces Integration

Prasoon — GMT

Hi Neil Griffin, I am newbie to icefaces. I have a basic understanding of JSF,Liferay. We are in the process of using icefaces components along with jsf and making it as a portlet and deploying on to the liferay[which is been configured on JBOSS 4.0.4 with Lifeary's war version.] I successfully able to run standalone icefaces, jsf application but when i am trying to make it as portlet i am getting these exceptions. 14:51:59,778 ERROR [PortletImpl] com.liferay.portal.NoSuchRoleException: No Role exists with the key {companyId=liferay.com, 14:52:05,153 ERROR [[TextFieldsPortlet]] Servlet.service() for servlet TextFieldsPortlet threw exception java.lang.ClassCastException: com.sun.faces.portlet.ExternalContextImpl at com.icesoft.faces.webapp.xmlhttp.PersistentFacesPortlet.render(PersistentFacesPortlet.java:226) at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at com.liferay.portlet.CachePortlet._invoke(CachePortlet.java:333) at com.liferay.portlet.CachePortlet.render(CachePortlet.java:182) at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:949) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:152) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:1102) at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:1048) at com.liferay.portal.action.RenderPortletAction.execute(RenderPortletAction.java:72) at com.liferay.portal.action.UpdateLayoutAction.execute(UpdateLayoutAction.java:168) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:156) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:477) at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:875) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:94) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.secure.SecureFilter.doFilter(SecureFilter.java:143) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:115) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:152) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) 14:52:05,153 ERROR [jsp] java.lang.ClassCastException: com.sun.faces.portlet.ExternalContextImpl at com.icesoft.faces.webapp.xmlhttp.PersistentFacesPortlet.render(PersistentFacesPortlet.java:226) at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at com.liferay.portlet.CachePortlet._invoke(CachePortlet.java:333) at com.liferay.portlet.CachePortlet.render(CachePortlet.java:182) at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:949) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268)Code:

I also try to deploy war file given by you and copied all the mentioned jars in my lib folder.I am getting this exception 14:37:35,508 ERROR [PortletImpl] com.liferay.portal.NoSuchRoleException: No Role exists with the key {companyId=liferay.com, name=admin} 14:37:38,633 ERROR [PersistentFacesPortlet] java.lang.NullPointerException at net.sf.jsfcomp.chartcreator.ChartListener.afterPhase(ChartListener.java:44) at com.sun.faces.portlet.LifecycleImpl.phase(LifecycleImpl.java:256) at com.sun.faces.portlet.LifecycleImpl.execute(LifecycleImpl.java:156) at com.icesoft.faces.webapp.xmlhttp.PersistentFacesPortlet.render(PersistentFacesPortlet.java:230) at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at com.liferay.portlet.CachePortlet._invoke(CachePortlet.java:333) at com.liferay.portlet.CachePortlet.render(CachePortlet.java:182) at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:949) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:152) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:1102) at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:1048) at com.liferay.portal.action.RenderPortletAction.execute(RenderPortletAction.java:72) at com.liferay.portal.action.UpdateLayoutAction.execute(UpdateLayoutAction.java:168) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:156) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:477) at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:875) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:94) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.secure.SecureFilter.doFilter(SecureFilter.java:143) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:115) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:152) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) Please help me in this regard.. Thanks in advance!!! Prasoon

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Prasoon, I think I know what is causing the first error. The PersistentFacesPortlet is assuming that the ICEfaces ExternalContext is already loaded by the JSF lifecycle. Please check your faces-config.xml file, and make sure that the element is present. In fact, please make sure that all of the following is present: Code:


 
  com.sun.faces.application.ViewHandlerImpl 
  
 
  com.icesoft.faces.application.D2DViewHandler 
  
 
  com.icesoft.faces.context.FacesContextFactoryImpl

Regarding your second error. I don't know. I think it may be caused if you are using one of the ICEfaces chart components. I am sorry but I did not have time to test the chart components. I was told by Ted Goddard of ICEsoft that they will be working on portlet support. I recommend that you download the ICEsoft source code, build it, and see if you can figure out where the problem is. Best Regards, Neil

Re:Liferay Portal-ICEfaces Integration

Prasoon — GMT

com.sun.faces.application.ViewHandlerImpl

com.icesoft.faces.application.D2DViewHandler

com.icesoft.faces.context.FacesContextFactoryImpl

textFields

bean.AutoCompleteBean

session

and this is my web.xml file

company_id

liferay.com

com.icesoft.faces.debugDOMUpdate

false

com.icesoft.faces.delegateNonIface

true

javax.faces.STATE_SAVING_METHOD

server

State saving method: "client" or "server" (= default) See JSF Specification 2.5.2

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Prasoon, The java.lang.NullPointerException at net.sf.jsfcomp.chartcreator.ChartListener.afterPhase(ChartListener.java:44) is probably due to the "chart creator jar file" that you wrote about. It has a JSF "Phase Listener", which will listen to every single JSF lifecycle phase, for every single JSF webapp (portlet) that you have. The "chart creator jar file" probably has a META-INF/faces-config.xml file inside it, which has a element. The JSF framework automatically looks for META-INF/faces-config.xml files inside of every .JAR in the WEB-INF/lib folder of a webapp. So that's why your ICEfaces portlet is running into trouble when you include the "chart creator jar file" in the other portlet. In order to understand why the "char creator jar file" is throwing the NullPointerException, you are going to have to download the source code for it and check out line 44 of ChartListener.java. Sorry I can't help any further with that. Now, it makes sense that the ChartListener.java exception goes away when you remove the "chart listener jar file." But now you are running into a java.lang.NullPointerException at com.icesoft.faces.application.D2DViewHandler.renderResponse(D2DViewHandler.java:498). Here is the offending code: Code:

    protected void renderResponse(FacesContext context) throws IOException {
        UIComponent root = context.getViewRoot();
        String viewId = ((UIViewRoot) root).getViewId();
        ...
        if ((root.getChildCount() == 0) || (reloadInterval > -1)) {
            // We have not parsed the page yet;
            // Need an input stream for the page;
            if (viewId.startsWith("/faces")) {

The viewId.startsWith() call is throwing the NullPointerException. That means that the earlier call to getViewId() is returning a null value. I suppose this can happen if your portlet.xml file is not setup correctly. For example, you might have an entry like this inside of portlet.xml Code:


  com.sun.faces.portlet.INIT_VIEW 
  /MyPage.iface

But perhaps there is a typo in the entry? Or perhaps your fileName is not MyPage.jspx in the filesystem. These are just guesses. By the way, are you using Facelets as your view handler? If you are, then you will need this in your faces-config.xml file: Code:


  com.icesoft.faces.facelets.D2DFaceletViewHandler

Note that my example portlet does not use Facelets. It uses standard .JSPX syntax. Also, it only uses and parameters -- it does not uses standard HTML tags like , , etc.. because I have just-ice.jar in the WEB-INF/lib folder (and not icefaces.jar). This is because I need DelegateNonIface=TRUE in the web.xml file. So if your WEB-INF/lib folder has just-ice.jar and not icefaces.jar, then you can't use standard html tags. See: http://www.icefaces.org/docs/v1_5_1/htmlguide/devguide/keyConcepts12.html Best Regards, Neil

Re:Liferay Portal-ICEfaces Integration

Prasoon — GMT

Hi Neil, sorry for the late response.I have still issues with the icefaces and liferay. I am not using facelets in my application. I am attaching my web application can you please check the source code and let me know if some changes are required, this will be a great help from you and also a learning experience for me. Please let me know my mistakes. Thanks & Regards Prasoon

Re:Liferay Portal-ICEfaces Integration

marios — GMT

Hello, I have a question regarding JSF portlet and ICEFaces Integration. I have a portlet (Liferay portlet actually) in JSF created by Java Studio Creator. I want to add only a page that uses ICEFaces inputFile component without messing with the rest pages. Is that possible? The developers Guide has a paragraph in page 17, "JSF Integration" that mentions this can be done, but the configurations that need to be done are not clear to me Can you give me some hints?

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Prasoon, Sorry for the delay -- I am super busy at work. I downloaded the .RAR file you posted but can't seem to extract it with the "jar xf" command. Can you please send it as a JAR/ZIP archive? Thanks, Neil

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Marios, I *think* it might be possible, but I don't know for sure. First of all, you need to decide if you are going to use icefaces.jar or just-ice.jar. When you use icefaces.jar, then all the standard components like will be ICE-Ajaxified, and can't be mixed with other JSF component libraries (like Java Studio Creator, Tomahawk) on the same page. Even though you are keeping your Java Studio Creator (JSC) pages separate from your ICEfaces fileUpload page, **my recommendation** is that you try just-ice.jar instead of icefaces.jar. Now, in your faces-config.xml file, you will need to try some interesting stuff. Your navigation rules will need to specify view Ids that are handled by different view handlers. For example:

MyNonIcePage.jsp

MyIceFileUploadPage.iface

I think you will also have to put the com.icesoft.faces.delegateNonIface=true context-param in your WEB-INF/web.xml file to instruct the D2DViewHandler to delegate non-ICEfaces type pages to another view handler. Good luck, Neil

Re:Liferay Portal-ICEfaces Integration

marios — GMT

Hello Neil, I tried to connect two pages, one in JSF and one in ICE in the same portlet. However only one works, and that seems to depend on whether I use com.icesoft.faces.webapp.xmlhttp.PersistentFacesPortlet where the ICE page works, or com.sun.faces.portlet.FacesPortlet where the JSF page works. Is there any way I can have both of them in the same portlet and say which pages will use which class? Marios

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

Marios, You should be able to use: portlet-class>com.icesoft.faces.webapp.xmlhttp.PersistentFacesPortlet And have your portlet between .jspx(ICEfaces) and .jsp (Non-ICEfaces) pages. This is because the delegateNonIface option instructs the D2DViewHandler to delegate view-id's other than .jspx to other registered view handlers (like the Sun JSF Reference Implementation View Handler). So if this doesn't work, then I would create an issue/bug in JIRA: http://jira.icefaces.org/secure/Dashboard.jspa

Re:Liferay Portal-ICEfaces Integration

Telpochyaotl — GMT

Hi! We are starting a pretty big project using liferay... I would very much love to use IceFaces in my portlets... What's the stage of integration? What's the roadmap? Thanks in advance!

Re:Liferay Portal-ICEfaces Integration

anmu — GMT

Hi all, has anybody made the component showcase work in a portlet? Is this possible with ICEfaces 1.6?

Re:Liferay Portal-ICEfaces Integration

jack.van.ooststroom — GMT

Just a little update on our progress. As you might have noticed we have released ICEfaces 1.6.0-DR#3 last week. This gave us the chance to commit our preliminary Portlet-support work into the trunk. Our nightly builds can now be used to exercise ICEfaces Portlets. ICEfaces Portlets must be configured to use our own custom MainPortlet (com.icesoft.faces.webapp.http.portlet.MainPortlet). In the case of the Liferay Portal, something like the following needs to be added to web.xml and portlet.xml respectively:

web.xml Code:


    timezone5
    com.liferay.portal.kernel.servlet.PortletServlet
    
        portlet-class
        com.icesoft.faces.webapp.http.portlet.MainPortlet
    
    0

portlet.xml Code:

com.icesoft.faces.webapp.http.portlet.MainPortlet

To define the initial view something like the following needs to be added to the portlet.xml:

portlet.xml Code:


    com.icesoft.faces.VIEW
    /timezone.iface

The JSF Portlet Bridge must not be used. It attempts to install it's own ViewHandler and such which interferes with ICEfaces' own. In fact anything that has it's own ViewHandler or other similar mechanisms should be examined to ensure they interact nicely with the ICEfaces framework. JavaScript collisions and its related problems is the most serious issue we are currently trying to address. In the case of Liferay it has JavaScript applied to the page that allows to do things like visually re-arrange individual Portlets by dragging. Adding an ICEfaces Portlet in the mix currently causes this feature to break. Another JavaScript collision occurs when attempting to run multiple ICEfaces Portlets on one page. Each ICEfaces Portlet tries to load its own copy of the JavaScript Bridge with its own configuration, which conflict. Other issues to be taken into account are: Getting Resources in Component Renderers Neil originally provided some patches for the 1.5 branch to properly locate external resources like images used for buttons. We have included the same logic for our ButtonRenderer for the time being, but we have to do a more thorough review of our renderers. Portlet vs. ICEfaces Themes Neil also logged an issue (and a potential strategy for fixing it) with a conflict between how a portal theme is applied and how it can conflict with our standard ICEfaces themes. However, it is currently possible to deploy an ICEfaces Portlet to Liferay on Tomcat or Jetty. We have been successful in porting our TimeZone tutorial examples into a Portlet Please refer to our main JIRA case ICE-147 at http://jira.icefaces.org/browse/ICE-1478 for more information. Regards,

Re:Liferay Portal-ICEfaces Integration

anmu — GMT

Hi Jack, thanks for this information: I have installed todays build of ICEfaces 1.6.0 and followed your instruction to make the timezone 5 tutorial example run in a portlet: I always get the following Exception: SEVERE: Servlet.service() for servlet ICEfacesTimezonePortlet threw exception java.lang.NullPointerException at com.icesoft.faces.webapp.http.portlet.MainPortlet.render(MainPortlet.java:93) at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at com.liferay.portlet.CachePortlet._invoke(CachePortlet.java:333) at com.liferay.portlet.CachePortlet.render(CachePortlet.java:182) at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:692) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) I also get the same Exception if I try to run the showcase in a portlet. Could you comment on this problem or provide your portlet war file for the timezone examples? Best regards Andreas

Re:Liferay Portal-ICEfaces Integration

jack.van.ooststroom — GMT

Andreas, It seems that the MainPortlet can't find a PortletRequestDispatcher to dispatch the incoming RenderRequest. Please make sure that your portlet.xml file contains the following configuration snippet: Code:

        
            com.icesoft.faces.VIEW
            /timezone.iface

Additionally, the MainServlet needs to be properly configured in the web.xml as well, as it needs to handle the dispatched request: Code:

    
        Main Servlet
        com.icesoft.faces.webapp.http.servlet.MainServlet
        1
    

    
        Main Servlet
        *.iface
    
    
        Main Servlet
        /xmlhttp/*
    
    
        Main Servlet
        /block/*

If this doesn't do the trick, please post your web.xml, portlet.xml and faces-config.xml so I can take a quick look. Regards,

Re:Liferay Portal-ICEfaces Integration

jack.van.ooststroom — GMT

Andreas, I forgot to mention that we are planning to post a war-file in the near future of an ICEfaces Portlet ready to be deployed in a Liferay/Tomcat environment. Regards,

Re:Liferay Portal-ICEfaces Integration

kirsten.powers — GMT

Regarding the following: "I forgot to mention that we are planning to post a war-file in the near future of an ICEfaces Portlet ready to be deployed in a Liferay/Tomcat environment." Is there an update on the progress? We are launching a portal project and will start development next month. The portal framework is Liferay 4.2 on JBoss, and we need a UI component library since the portlets will be developed by teams across the globe. We very much want to use ICEfaces for the component library, but if portlet support it too difficult to achieve we will have to look elsewhere. Please let us know...

Re:Liferay Portal-ICEfaces Integration

jack.van.ooststroom — GMT

Hi Kirsten, Unfortunately we don't have a fixed date yet for our ICEfaces Portlet example(s). However, Liferay 4.3.0 with preliminary ICEfaces integration (ICEfaces 1.6-DR#5) will be available “early next week” at Liferay. This release will contain an ICEfaces Portlet example named sample-jsf-icefaces-sunh-portlet.war using Sun RI (no MyFaces yet). Liferay 4.3.1 will feature ICEfaces 1.6-production. We are closely working together with the people at Liferay to get our Portlet-support up to speed. Our upcoming ICEfaces 1.6-DR#5 will include more of our Portlet-support improvements. Please note that our initial supported platform is Liferay/Tomcat, but we'll be glad to help out getting it to run on Liferay/Jboss. Regards,

Re:Liferay Portal-ICEfaces Integration

kirsten.powers — GMT

I just downloaded the rc4.3 candidate of liferay portal. The icefaces portlet example that you referred to does not appear to be included. Is this downloadable separately from ICEsoft?

Re:Liferay Portal-ICEfaces Integration

philip.breau — GMT

Hi Kirsten, The ICEfaces sample can be downloaded separately from the SourceForge site. http://sourceforge.net/project/showfiles.php?group_id=49260&package_id=42607&release_id=511986 Philip

Re:Liferay Portal-ICEfaces Integration

ngriffin7a — GMT

You can also find the Sample ICEfaces portlet on Liferay's Samples page: http://www.liferay.com/web/guest/downloads/samples Neil Griffin Liferay, Inc.

Re:Liferay Portal-ICEfaces Integration

ken.fyten — GMT

Folks, as most of this long thread predates the release of the initial Liferay + ICEfaces integration I'm going to lock it now. Please create new threads for future Liferay - ICEfaces topics. Regards, Ken