ICEfaces
  1. ICEfaces
  2. ICE-4704

Add warning message to log when JSF 2.0 is detected in ICEfaces 1.x

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.1
    • Fix Version/s: 1.8.2-RC1, 1.8.2
    • Component/s: Documentation, Framework
    • Labels:
      None
    • Environment:
      ICEfaces 1.8.x with JSF 2.0 runtimes, such as Glassfish v3 Preview.
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration

      Description

      ICEfaces 1.8.x is not certified to run on JSF 2.0 runtimes. When this combination is attempted with ICEfaces 1.8.1, it fails with an exception such as

      java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2

      ...rather than logging confusing exceptions we should add detection for JSF 2 and log an informative message, such as: "This version of ICEfaces does not support JSF 2.0. JSF 1.2 is recommended. For JSF 2.0 support ICEfaces 2.0 is recommended."

        Activity

        Hide
        Deryk Sinotte added a comment -

        I've added a check for JSF 2.0 and a warning level log message that indicates that the current version of ICEfaces is not supported on 2.0 but have not thrown any exception that would terminate the application as we have some experimental code for running on JSF 2.0 in the core (although it's currently not operational).

        Show
        Deryk Sinotte added a comment - I've added a check for JSF 2.0 and a warning level log message that indicates that the current version of ICEfaces is not supported on 2.0 but have not thrown any exception that would terminate the application as we have some experimental code for running on JSF 2.0 in the core (although it's currently not operational).
        Hide
        Joanne Bai added a comment -

        Tested successfully on ICEfaces trunk revision 19228 + Glassfish v3 preview using component showcase jsp

        The following massage displays in the server log:
        [#|2009-09-06T14:19:40.747-0600|WARNING|glassfish|com.icesoft.faces.application.D2DViewHandler|_ThreadID=17;_ThreadName=Thread-1;|JSF 2.0 libraries detected. This version of ICEfaces is not supported on JSF 2.0. JSF 1.1 or 1.2 are required.|#]

        On browser (FF3.5), the following shows:
        descriptionThe server encountered an internal error () that prevented it from fulfilling this request.

        exception

        javax.servlet.ServletException: java.lang.Exception: java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2

        root cause

        java.lang.Exception: java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2

        root cause

        java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2

        Show
        Joanne Bai added a comment - Tested successfully on ICEfaces trunk revision 19228 + Glassfish v3 preview using component showcase jsp The following massage displays in the server log: [#|2009-09-06T14:19:40.747-0600|WARNING|glassfish|com.icesoft.faces.application.D2DViewHandler|_ThreadID=17;_ThreadName=Thread-1;|JSF 2.0 libraries detected. This version of ICEfaces is not supported on JSF 2.0. JSF 1.1 or 1.2 are required.|#] On browser (FF3.5), the following shows: descriptionThe server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: java.lang.Exception: java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2 root cause java.lang.Exception: java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2 root cause java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2

          People

          • Assignee:
            Deryk Sinotte
            Reporter:
            Ken Fyten
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: