ICEfaces
  1. ICEfaces
  2. ICE-11500

Add support for Eclipse Mojarra JSF 2.3

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EE-3.3.0.GA_P07
    • Fix Version/s: EE-3.3.0.GA_P08
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Eclipse Mojarra 2.3

      Description

      At the moment, EE 3.3 demo applications using Eclipse Mojarra JSF 2.3 fail in different ways. For example, on the showcase, it's not possible to interact with the non-overview demos. The browser console shows messages like "javax.faces.ViewState not found" and "jsf.ajax.request: Form has no view state element" when making an ajax request on a non-overview demo.

      Support for JSF 2.3 was added to the 4.x codebase as per ICE-11212.

      I did a quick test of modifying the EnvUtils.isJSF22() method to return true when the version starts with "2.3", and things seem to work well when deploying the showcase with this change. However, the real fix would need to be more robust and have other considerations.

      This JIRA is to add support for Eclipse Mojarra JSF 2.3, while still supporting (Oracle) Mojarra 2.1 and 2.2.

      Note that it's also necessary to have the cdi-api-1.2.jar or cdi-api-2.0.jar in the classpath of the application in order to avoid java.lang.NoClassDefFoundError exceptions.

      This is being tested with the latest 2.3.* Eclipse Mojarra version, which is 2.3.14, which can be found at this URL:
      https://github.com/eclipse-ee4j/mojarra/releases

      This is the Eclipse Mojarra site, which contains more information:
      https://eclipse-ee4j.github.io/mojarra/

        Activity

        Arturo Zambrano created issue -
        Arturo Zambrano made changes -
        Field Original Value New Value
        Assignee Mircea Toma [ mircea.toma ]
        Arturo Zambrano made changes -
        Fix Version/s EE-3.3.0.GA_P08 [ 13293 ]
        Arturo Zambrano made changes -
        Environment Eclipse Mojarra Eclipse Mojarra 2.3
        Arturo Zambrano made changes -
        Description At the moment, EE 3.3 demo applications using Eclipse Mojarra JSF 2.3 fail in different ways. For example, on the showcase, it's not possible to interact with the non-overview demos. The browser console shows messages like "javax.faces.ViewState not found" and "jsf.ajax.request: Form has no view state element" when making an ajax request on a non-overview demo.

        Support for JSF 2.3 was added to the 4.x codebase as per ICE-11212.

        I did a quick test of modifying the EnvUtils.isJSF22() method to return true when the version starts with "2.3", and things seem to work well when deploying the showcase with this change. However, the real fix would need to be more robust and have other considerations.

        Note that it's also necessary to have the cdi-api-1.2.jar or cdi-api-2.0.jar in the classpath of the application in order to avoid java.lang.NoClassDefFoundError exceptions.

        This is being tested with the latest 2.3.* Eclipse Mojarra version, which is 2.3.14, which can be found at this URL:
        https://github.com/eclipse-ee4j/mojarra/releases

        This is the Eclipse Mojarra site, which contains more information:
        https://eclipse-ee4j.github.io/mojarra/
        At the moment, EE 3.3 demo applications using Eclipse Mojarra JSF 2.3 fail in different ways. For example, on the showcase, it's not possible to interact with the non-overview demos. The browser console shows messages like "javax.faces.ViewState not found" and "jsf.ajax.request: Form has no view state element" when making an ajax request on a non-overview demo.

        Support for JSF 2.3 was added to the 4.x codebase as per ICE-11212.

        I did a quick test of modifying the EnvUtils.isJSF22() method to return true when the version starts with "2.3", and things seem to work well when deploying the showcase with this change. However, the real fix would need to be more robust and have other considerations.

        This JIRA is to add support for Eclipse Mojarra JSF 2.3, while still supporting (Oracle) Mojarra 2.1 and 2.2.

        Note that it's also necessary to have the cdi-api-1.2.jar or cdi-api-2.0.jar in the classpath of the application in order to avoid java.lang.NoClassDefFoundError exceptions.

        This is being tested with the latest 2.3.* Eclipse Mojarra version, which is 2.3.14, which can be found at this URL:
        https://github.com/eclipse-ee4j/mojarra/releases

        This is the Eclipse Mojarra site, which contains more information:
        https://eclipse-ee4j.github.io/mojarra/
        Mircea Toma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Arturo Zambrano
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: