Affects Version/s: None
Fix Version/s: None
Environment:IBM WebSphere 6
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.