ICEfaces
  1. ICEfaces
  2. ICE-2330

Deploy icefaces application to Websphere 6.1

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: 1.7
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            Websphere 6.1
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            To get around the problem:
            - remove xml-api.jar from application bundle
            - configure the web module of the application to use application classloader (not WAR classloader) and set class loading order to "parent_last"
            Show
            To get around the problem: - remove xml-api.jar from application bundle - configure the web module of the application to use application classloader (not WAR classloader) and set class loading order to "parent_last"

            Description

            Problem found deploying icefaces sample application to Websphere 6.1 (address-demo):
            - common-logging.jar already included in Websphere 6.1, may cause conflict (suggest to remove it from application bundle but we can live with it)
            - WAS includes xalan and modifed javax.xml.* classes in deploy.jar (must remove xml-api.jar from application bundle)
            - WAS 6.1 requires IBM JWL (JavaServer Faces widget library) version 2.0 jar files (if not faces-config.xml cannot be correctly processed and thus cause jsf failure. not go to next page for address demo)

              Activity

              Hide
              Permalink
              Jacky Lee added a comment -

              Instructions for configuring Websphere for the workaround:

              1) In the Websphere admin console, go to Appication -> Enterprise Applications
              2) Click on your application name
              3) Click on "Class loading and update detection"
              4) Give some value for "Polling interval for updated files" as this is a required input
              5) Set "Class loader order" to "Classes loaded with application class loader first"
              6) Set "WAR class loader policy" to "Single class loader for application"
              7) Click "Apply" and save master configuration

              Show
              Jacky Lee added a comment - Instructions for configuring Websphere for the workaround: 1) In the Websphere admin console, go to Appication -> Enterprise Applications 2) Click on your application name 3) Click on "Class loading and update detection" 4) Give some value for "Polling interval for updated files" as this is a required input 5) Set "Class loader order" to "Classes loaded with application class loader first" 6) Set "WAR class loader policy" to "Single class loader for application" 7) Click "Apply" and save master configuration

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Sam Xiao
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: