ICEfaces
  1. ICEfaces
  2. ICE-3682

Certify ICEfaces on Glassfish v3

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.8RC1, 1.8
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Glassfish v3 "Prelude"
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration

      Description

      Need to certify ICEfaces for use on Glassfish v3 (Prelude is the latest pre-release version).

        Issue Links

          Activity

          Hide
          Joanne Bai added a comment -

          There is no glassfish v3 target yet. Built the sample apps using ant glassfishv2.

          Address, auctionMonitor, component-showcase (jsp vsersioin) can be deployed, but not loaded from firefox.

          Show
          Joanne Bai added a comment - There is no glassfish v3 target yet. Built the sample apps using ant glassfishv2. Address, auctionMonitor, component-showcase (jsp vsersioin) can be deployed, but not loaded from firefox.
          Hide
          Deryk Sinotte added a comment -

          I downloaded Glassfish V3 Prelude. One thing I noticed is that the JSF version that came with it (based on the manifest info):

          Bundle-Description: Mojarra JSF API (javax.faces/1.2MR2) 1.2_10-b01-FC

          When I ran the Admin Console, it said there was one update available:

          Component Category Installed Version New Version Change Source
          glassfish-jsf Application Servers 1.2.10-1 2.0.0-7 717KB dev.glassfish.org

          So according to the current GFV3 that I downloaded, everything should be good to go. So I built Comp Show Facelets edition using the glassfishv2 build target and deployed it to my default domain. The logging didn't show anything unusual other than our own Comet message:

          [#|2008-12-17T21:25:47.230-0800|SEVERE|glassfish|com.icesoft.faces.webapp.http.servlet.GlassFishAdaptingServlet|_ThreadID=21;_ThreadName=Thread-3;|

          Failed to add Comet handler:
          Exception message: Make sure you have enabled Comet or make sure the Thread invoking that method is the same a the request Thread.
          Exception cause: null

          To enable GlassFish ARP, please set the cometSupport property to true in the
          domain's config/domain.xml for the http-listener listening to port 8080.

          #]

          Other than that, it worked fine. When I ran Auction Monitor, I got the originally reported errors:

          [#|2008-12-17T21:31:42.298-0800|SEVERE|glassfish|com.icesoft.faces.webapp.parser.JspPageToDocument|_ThreadID=15;_ThreadName=Thread-3;|Can't find TLD for location http://java.sun.com/jsf/html. JAR containing the TLD may not be in the classpath|#]

          [#|2008-12-17T21:31:42.461-0800|SEVERE|glassfish|com.icesoft.faces.webapp.parser.JspPageToDocument|_ThreadID=15;_ThreadName=Thread-3;|Can't find TLD for location http://java.sun.com/jsf/core. JAR containing the TLD may not be in the classpath|#]

          [#|2008-12-17T21:31:42.776-0800|SEVERE|glassfish|com.icesoft.faces.webapp.parser.Parser|_ThreadID=15;_ThreadName=Thread-3;|Failed to execute JSP lifecycle.
          java.lang.IllegalStateException: ICEfaces parser unable to determine JSF implementation ViewTag class.
          at com.icesoft.faces.webapp.parser.Parser.parse(Parser.java:154)
          at com.icesoft.faces.application.D2DViewHandler.renderResponse(D2DViewHandler.java:501)
          at com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:156)
          at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110)
          ...

          So it appears that maybe our Facelets based apps work but our JSP based apps do not.

          Show
          Deryk Sinotte added a comment - I downloaded Glassfish V3 Prelude. One thing I noticed is that the JSF version that came with it (based on the manifest info): Bundle-Description: Mojarra JSF API (javax.faces/1.2MR2) 1.2_10-b01-FC When I ran the Admin Console, it said there was one update available: Component Category Installed Version New Version Change Source glassfish-jsf Application Servers 1.2.10-1 2.0.0-7 717KB dev.glassfish.org So according to the current GFV3 that I downloaded, everything should be good to go. So I built Comp Show Facelets edition using the glassfishv2 build target and deployed it to my default domain. The logging didn't show anything unusual other than our own Comet message: [#|2008-12-17T21:25:47.230-0800|SEVERE|glassfish|com.icesoft.faces.webapp.http.servlet.GlassFishAdaptingServlet|_ThreadID=21;_ThreadName=Thread-3;| Failed to add Comet handler: Exception message: Make sure you have enabled Comet or make sure the Thread invoking that method is the same a the request Thread. Exception cause: null To enable GlassFish ARP, please set the cometSupport property to true in the domain's config/domain.xml for the http-listener listening to port 8080. #] Other than that, it worked fine. When I ran Auction Monitor, I got the originally reported errors: [#|2008-12-17T21:31:42.298-0800|SEVERE|glassfish|com.icesoft.faces.webapp.parser.JspPageToDocument|_ThreadID=15;_ThreadName=Thread-3;|Can't find TLD for location http://java.sun.com/jsf/html . JAR containing the TLD may not be in the classpath|#] [#|2008-12-17T21:31:42.461-0800|SEVERE|glassfish|com.icesoft.faces.webapp.parser.JspPageToDocument|_ThreadID=15;_ThreadName=Thread-3;|Can't find TLD for location http://java.sun.com/jsf/core . JAR containing the TLD may not be in the classpath|#] [#|2008-12-17T21:31:42.776-0800|SEVERE|glassfish|com.icesoft.faces.webapp.parser.Parser|_ThreadID=15;_ThreadName=Thread-3;|Failed to execute JSP lifecycle. java.lang.IllegalStateException: ICEfaces parser unable to determine JSF implementation ViewTag class. at com.icesoft.faces.webapp.parser.Parser.parse(Parser.java:154) at com.icesoft.faces.application.D2DViewHandler.renderResponse(D2DViewHandler.java:501) at com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:156) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) ... So it appears that maybe our Facelets based apps work but our JSP based apps do not.
          Hide
          Ken Fyten added a comment -

          Ted G. committed a fix for the TLD class-loading issue under ICE-3902 that was also applied to trunk:

          Repository Revision Date User Message
          ICEfaces Repository #18092 Fri Dec 19 09:47:30 CST 2008 ted.goddard look for JSF TLDs in bundles on GlassFishv3 (ICE-3902)
          Files Changed
          MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/parser/JspPageToDocument.java

          Show
          Ken Fyten added a comment - Ted G. committed a fix for the TLD class-loading issue under ICE-3902 that was also applied to trunk: Repository Revision Date User Message ICEfaces Repository #18092 Fri Dec 19 09:47:30 CST 2008 ted.goddard look for JSF TLDs in bundles on GlassFishv3 ( ICE-3902 ) Files Changed MODIFY /icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/parser/JspPageToDocument.java
          Hide
          Mandeep Hayher added a comment -

          ICEFaces trunk (revision# 18154) sample applications tested successfuly on Glassfishv3-prelude server using browsers FF3, IE7 & Opera9.63.
          NOTE: All applications were built using glassfishv2 target.

          Show
          Mandeep Hayher added a comment - ICEFaces trunk (revision# 18154) sample applications tested successfuly on Glassfishv3-prelude server using browsers FF3, IE7 & Opera9.63. NOTE: All applications were built using glassfishv2 target.

            People

            • Assignee:
              Unassigned
              Reporter:
              Ken Fyten
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: