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

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        3d 22h 41m 1 Malcolm Edgar 11/Oct/05 06:26
        Resolved Resolved Closed Closed
        6d 2h 4m 1 Malcolm Edgar 17/Oct/05 08:30
        Henri Yandell made changes -
        Project Import Fri Mar 20 14:11:32 PDT 2009 [ 1237583492744 ]
        Malcolm Edgar made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Hide
        Malcolm Edgar added a comment -

        Fix validated on WS.

        Next release 0.14 will remove JDOM dependency.

        Show
        Malcolm Edgar added a comment - Fix validated on WS. Next release 0.14 will remove JDOM dependency.
        Malcolm Edgar made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Malcolm Edgar added a comment -

        Added JDOM 0.7 compliance build step to ensure no post JDOM 0.7 methods are called. This should prevent IBM WepSphere application server JDOM class loader issues.

        This fix is checked into CVS and will be available in release 0.13.

        Show
        Malcolm Edgar added a comment - Added JDOM 0.7 compliance build step to ensure no post JDOM 0.7 methods are called. This should prevent IBM WepSphere application server JDOM class loader issues. This fix is checked into CVS and will be available in release 0.13.
        Hide
        Malcolm Edgar added a comment -

        I think I have figured it out this class loader issue.

        Click release 0.7 started using the JDOM Element method getAttribute(String, String) which is not available in JDOM 0.7.

        I have modified the Click code base (ClickApp, Menu) to build against JDOM 0.7 to ensure compatablity with WAS.

        Show
        Malcolm Edgar added a comment - I think I have figured it out this class loader issue. Click release 0.7 started using the JDOM Element method getAttribute(String, String) which is not available in JDOM 0.7. I have modified the Click code base (ClickApp, Menu) to build against JDOM 0.7 to ensure compatablity with WAS.
        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 -
        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. ]
        Hide
        Malcolm Edgar added a comment -
        Show
        Malcolm Edgar added a comment - This JDOM issue is also described here: http://www.openlaszlo.org/pipermail/laszlo-user/2004-November/000000.html
        Malcolm Edgar created issue -

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development