Title | problems with common-logging |
Date | 31-May-2006 16:05:59 EEST |
Version | v2.4.6 |
Submitter | 193.134.254.145 |
Bug criticality | LightBug |
Browser version | Firefox |
Bug status | ClosedBug |
PageProvider used | |
Servlet Container | WebSphere |
Operating System | Sun Solaris |
URL | |
Java version | 1.4.2 |
Within WebSphere: For JSPWiki not to get in trouble with "jdom", you have to set the classloader mode to "PARENT_LAST". But this mixes the classloading for the LogFactory. To get around this problem I replaced the "commons-logging-api.jar" with the "commons-logging-adapters-1.1.jar". But now I get to the next problem:
[5/31/06 14:49:49:495 MEST] 1908404 WebGroup E SRVE0026E: [Servlet Error]-[loader constraints violated when linking org/xml/sax/DTDHandler class]: java.lang.LinkageError: loader constraints violated when linking org/xml/sax/DTDHandler class at org.jdom.input.SAXBuilder.configureParser(SAXBuilder.java:614) at org.jdom.input.SAXBuilder.build(SAXBuilder.java:440) at org.jdom.input.SAXBuilder.build(SAXBuilder.java:810) at com.ecyrd.jspwiki.plugin.PluginManager.registerPlugins(PluginManager.java:671) at com.ecyrd.jspwiki.plugin.PluginManager.<init>(PluginManager.java:180) at com.ecyrd.jspwiki.WikiEngine.initialize(WikiEngine.java:527)Any ideas?
best regards Domi
JDOM and Websphere seem to be very problematic. I would appreciate it if someone wrote in once and for all how those two should get together...
As said, the solution would be to change the classloader mode - but this does not solve it this time... Domi
It is important to note that you should change the classloader mode of the webapplication, and not the classloader mode of the enterprise application.
Harry Metske
--HarryMetske, 29-Jun-2006
If you do this within WebSphere (copied from above)
For JSPWiki not to get in trouble with "jdom", you have to set the classloader mode to "PARENT_LAST". But this mixes the classloading for the LogFactory. To get around this problem I replaced the "commons-logging-api.jar" with the "commons-logging-adapters-1.1.jar".
And also remove xmlrpc.jar it will work... woohoo!!!
--Romano Silva, 24-Aug-2006
So the problem seems to be solved , closing the bug.