Vernon Singleton added a comment - 19/Dec/14 3:38 PM - edited Steps to reproduce: 1. Download a showcase war 2. Deploy the war in the webapp folder of a running Liferay tomcat bundle . 3. Navigate to the localhost/showcase url Expected results: The showcase should render. Actual results: The showcase does not render, and the following errors/warnings appear in catalina.out: WARNING: JSF1086: Custom scope '#{window}' evaluated to null . Unable to determine if managed bean exists. Dec 19, 2014 10:30:45 PM com.sun.faces.mgbean.BeanManager$ScopeManager$CustomScopeHandler handle WARNING: JSF1085: Custom scope '#{window}' evaluated to null . Managed bean was not pushed to scope. Dec 19, 2014 10:30:45 PM org.icefaces.impl.event.BridgeSetup getBodyResources WARNING: Unable to find WindowScope for view /showcase.xhtml

Vernon Singleton added a comment - 19/Dec/14 3:51 PM - edited This issue can be fixed at this block of code inside of the the WindowScopeManager: private LiferayOriginalRequestWindowScopeSharing() throws ClassNotFoundException, NoSuchMethodException { PortalUtilClass = Class .forName( "com.liferay.portal.util.PortalUtil" ); GetHttpServletRequest = PortalUtilClass.getDeclaredMethod( "getHttpServletRequest" , javax.portlet.PortletRequest.class); GetOriginalServletRequest = PortalUtilClass.getDeclaredMethod( "getOriginalServletRequest" , HttpServletRequest.class); } Instead of assuming the the icefaces core jar is being used by a portlet with the Class.forName method used above, a different method could be used to determine if the icefaces core is being used by a webapp or a portlet (Maybe check the application for the existence of a portlet.xml resource). And if no portlet.xml is found, for example, then you could throw an exception.

Mircea Toma added a comment - 12/Jan/15 1:23 PM Applied recommended fix that verifies if we're indeed running within Liferay and not as a parallel webapp to Liferay webapp.