Click
  1. Click
  2. CLK-25

IBM WebSphere 6 class loader issues

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
       IBM WebSphere 6

      Description

      Oliver Burn reports that IBM WebSphere 6 has classloader issues on the JDOM libary used in Click 0.12.

      IBM WebSphere internally uses JDOM 1.0 beta 7

      Click version 0.3 to 0.12 uses JDOM 1.0

      Note this issue does not occur with Click 0.6 which also uses JDOM 1.0.

      The WebSphere commons-logging issue was not implicated as click-extras.jar, which contains commons-logging was not used.

      Note commons-logging is due to be replaced with Log4J in release 0.13 to avoid WebSphere classloader issues.

      One possible solution is to build Click against JDOM 0.7 to ensure no new JDOM 1.0 methods are called, so if WAS uses JDOM 0.7 it won't choke.

        Activity

        Malcolm Edgar created issue -
        Malcolm Edgar made changes -
        Field Original Value New Value
        Comment [ Possible solution is to build Click against JDOM 0.7 to ensure no new JDOM 1.0 are called, so if WAS uses JDOM 0.7 it won't choke. ]
        Malcolm Edgar made changes -
        Description Oliver Burn reports that IBM WebSphere 6 has classloader issues on the JDOM libary used in Click 0.12.

        IBM WebSphere internally uses JDOM 1.0 beta 7

        Click version 0.3 to 0.12 uses JDOM 1.0

        Note this issue does not occur with Click 0.6 which also uses JDOM 1.0.

        The WebSphere commons-logging issue was not implicated as click-extras.jar, which contains commons-logging was not used.

        Note commons-logging is due to be replaced with Log4J in release 0.13 to avoid WebSphere classloader issues.
        Oliver Burn reports that IBM WebSphere 6 has classloader issues on the JDOM libary used in Click 0.12.

        IBM WebSphere internally uses JDOM 1.0 beta 7

        Click version 0.3 to 0.12 uses JDOM 1.0

        Note this issue does not occur with Click 0.6 which also uses JDOM 1.0.

        The WebSphere commons-logging issue was not implicated as click-extras.jar, which contains commons-logging was not used.

        Note commons-logging is due to be replaced with Log4J in release 0.13 to avoid WebSphere classloader issues.

        One possible solution is to build Click against JDOM 0.7 to ensure no new JDOM 1.0 methods are called, so if WAS uses JDOM 0.7 it won't choke.
        Malcolm Edgar made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Malcolm Edgar made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Henri Yandell made changes -
        Project Import Fri Mar 20 14:11:32 PDT 2009 [ 1237583492744 ]

          People

          • Assignee:
            Malcolm Edgar
            Reporter:
            Malcolm Edgar
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development