ICEfaces
  1. ICEfaces
  2. ICE-1474

ICEfaces doesn't work in pure JSF 1.2 mode

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6DR#3
    • Fix Version/s: 1.8.2
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      WinXP SP2, Firefox 1.5.0.11, glassfish v1_ur1-p01-b02, component-showcase-facelets
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      Use the old JSF 1.1 DTD syntax in the faces-config.xml and web.xml files of your web application.
      Show
      Use the old JSF 1.1 DTD syntax in the faces-config.xml and web.xml files of your web application.

      Description

      When JSF 1.2 compatibility was coded for ICEfaces 1.6.0 DR3, the test applications used JSF 1.1 DTD syntax in the faces-config.xml and web.xml files, not the newer JSF 1.2 XMLSchema syntax. It turns out, that has an affect of running the JSF 1.2 RI code in a JSF 1.1 compatibility mode. So while ICEfaces works in the compatibility mode, it does not work in the pure mode. It would be good to work in either mode.

        Issue Links

          Activity

          Hide
          Ken Fyten added a comment -

          ICEfaces 1.5, 1.6 do not support JSF 1.2 runtimes with JSPs. This is the reason for the failures running the Address Demo.

          Note that beginning with ICEfaces 1.6 running on JSF 1.2 runtimes, such as that included with JBoss 4.2, is supported for Facelet applications only. Thus, the Facelet sample applications such as the Facelet Comp. Showcase and Timezone #7 will work correctly on JBoss 4.2.

          Show
          Ken Fyten added a comment - ICEfaces 1.5, 1.6 do not support JSF 1.2 runtimes with JSPs. This is the reason for the failures running the Address Demo. Note that beginning with ICEfaces 1.6 running on JSF 1.2 runtimes, such as that included with JBoss 4.2, is supported for Facelet applications only. Thus, the Facelet sample applications such as the Facelet Comp. Showcase and Timezone #7 will work correctly on JBoss 4.2.
          Hide
          Ted Goddard added a comment -

          Progress in ICE-1699 allows JSP-based ICEfaces applications to be used with JSF 1.2 libraries.

          Show
          Ted Goddard added a comment - Progress in ICE-1699 allows JSP-based ICEfaces applications to be used with JSF 1.2 libraries.
          Hide
          Ted Goddard added a comment -

          There must be specific features that fail outside the JSF 1.1 compatibility mode. I just tested auctionMonitor with XSI-based web.xml and faces-config.xml on glassfish and it shows no problems.

          Show
          Ted Goddard added a comment - There must be specific features that fail outside the JSF 1.1 compatibility mode. I just tested auctionMonitor with XSI-based web.xml and faces-config.xml on glassfish and it shows no problems.
          Hide
          Ted Goddard added a comment -

          Superficial testing with component-showcase (JSP) on glassfish with JSF 1.2 shows no complications with the following entries in web.xml and faces-config.xml respectively:

          <web-app version="2.5"
          xmlns="http://java.sun.com/xml/ns/javaee"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">

          <faces-config xmlns="http://java.sun.com/xml/ns/javaee"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"
          version="1.2">

          The reported problems may be facelets-specific or may not be present in the current build.

          Show
          Ted Goddard added a comment - Superficial testing with component-showcase (JSP) on glassfish with JSF 1.2 shows no complications with the following entries in web.xml and faces-config.xml respectively: <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd "> <faces-config xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd " version="1.2"> The reported problems may be facelets-specific or may not be present in the current build.
          Hide
          Gary Murphy added a comment -

          I am having the same problem on Tomcat 6.0.13. The exception stack looks like:

          Aug 7, 2007 5:19:26 PM com.icesoft.faces.application.D2DViewHandler <clinit>
          INFO:
          ICEsoft Technologies, Inc.
          ICEfaces 1.6.0
          Build number: 15
          Revision: 14409

          Aug 7, 2007 5:19:42 PM com.sun.faces.lifecycle.LifecycleImpl phase
          WARNING: executePhase(RESTORE_VIEW 1,com.icesoft.faces.context.BridgeFacesContext@abe654) threw exception
          javax.faces.application.ViewExpiredException: viewId:/logon.faces - View /logon.faces could not be restored.
          at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:185)
          at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
          at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
          at com.icesoft.faces.webapp.http.core.PageServer$1.respond(PageServer.java:25)
          at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:125)
          at com.icesoft.faces.webapp.http.core.PageServer.service(PageServer.java:31)
          at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
          at com.icesoft.faces.webapp.http.servlet.SingleViewServlet.service(SingleViewServlet.java:45)
          at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
          at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
          at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97)
          at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35)
          at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
          at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
          at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
          at java.lang.Thread.run(Thread.java:595)

          Show
          Gary Murphy added a comment - I am having the same problem on Tomcat 6.0.13. The exception stack looks like: Aug 7, 2007 5:19:26 PM com.icesoft.faces.application.D2DViewHandler <clinit> INFO: ICEsoft Technologies, Inc. ICEfaces 1.6.0 Build number: 15 Revision: 14409 Aug 7, 2007 5:19:42 PM com.sun.faces.lifecycle.LifecycleImpl phase WARNING: executePhase(RESTORE_VIEW 1,com.icesoft.faces.context.BridgeFacesContext@abe654) threw exception javax.faces.application.ViewExpiredException: viewId:/logon.faces - View /logon.faces could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:185) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at com.icesoft.faces.webapp.http.core.PageServer$1.respond(PageServer.java:25) at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:125) at com.icesoft.faces.webapp.http.core.PageServer.service(PageServer.java:31) at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16) at com.icesoft.faces.webapp.http.servlet.SingleViewServlet.service(SingleViewServlet.java:45) at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97) at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35) at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595)
          Hide
          Brahm Broom added a comment -

          I'm trying to use ICEfaces 1.6 with facelets (using the icefaces-facelets jar) and JSF 1.2 with the Sun-RI implementation. I'm encountering the same problem. I get the following stack trace when I try to run a sample app using the XMLSchema syntax for both the web and faces-config xml files:

          javax.faces.application.ViewExpiredException: viewId:/intro.iface - View /intro.iface could not be restored.
          com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:187)
          com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
          com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
          com.icesoft.faces.webapp.http.core.PageServer$1.respond(PageServer.java:25)
          com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:125)
          com.icesoft.faces.webapp.http.core.PageServer.service(PageServer.java:31)
          com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
          com.icesoft.faces.webapp.http.servlet.MultiViewServlet.service(MultiViewServlet.java:53)
          com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
          com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
          com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97)
          com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35)
          com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
          com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
          com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85)
          javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
          org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:694)
          org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:665)
          org.apache.jsp.index_jsp._jspService(index_jsp.java:54)
          org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
          javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
          org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
          org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
          org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
          javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

          I was able to get it working (workaround) by using the JSF 1.1 DTD syntax for faces-config.xml. I did NOT need to change my JSF 1.2 XMLSchema syntax for web.xml.

          So, to sum up, my workaround involved a DTD syntax for faces-config.xml and XMLSchema syntax for web.xml.

          Show
          Brahm Broom added a comment - I'm trying to use ICEfaces 1.6 with facelets (using the icefaces-facelets jar) and JSF 1.2 with the Sun-RI implementation. I'm encountering the same problem. I get the following stack trace when I try to run a sample app using the XMLSchema syntax for both the web and faces-config xml files: javax.faces.application.ViewExpiredException: viewId:/intro.iface - View /intro.iface could not be restored. com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:187) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) com.icesoft.faces.webapp.http.core.PageServer$1.respond(PageServer.java:25) com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith(ServletRequestResponse.java:125) com.icesoft.faces.webapp.http.core.PageServer.service(PageServer.java:31) com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16) com.icesoft.faces.webapp.http.servlet.MultiViewServlet.service(MultiViewServlet.java:53) com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97) com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35) com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:694) org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:665) org.apache.jsp.index_jsp._jspService(index_jsp.java:54) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) I was able to get it working (workaround) by using the JSF 1.1 DTD syntax for faces-config.xml. I did NOT need to change my JSF 1.2 XMLSchema syntax for web.xml. So, to sum up, my workaround involved a DTD syntax for faces-config.xml and XMLSchema syntax for web.xml.
          Hide
          Martin Marquez added a comment -

          Brahm, Can you post your configuration? I'm still having this problem, regards.

          Show
          Martin Marquez added a comment - Brahm, Can you post your configuration? I'm still having this problem, regards.

            People

            • Assignee:
              Unassigned
              Reporter:
              Mark Collette
            • Votes:
              13 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: