commons-crap

[kristoff]

Ok, so I have an MDB that uses org.apache.commons.httpclient

When I upgraded to 3.2.1, the first problem came from the fact that it now comes with commons-httpclient.jar in <jboss-home>/lib

So, I replaced it with the newer version that I need, and then I get errors related to commons-logging stuff. So I put the commons-logging jar in <jboss-home>/lib and I get classdef not found errors pertaining to the logging stuff.

The only way I got this to work was to move both of the commons-crap.jar files to <jboss-home>/server/default/lib

Can someone explain what is happening here? I really want to understand the issue. Also, why is commons-httpclient now part of JBoss? Presumably for clustering support? I see no mention of it in any of the change notes.

TIA.

[jdbrown]

I also am having a problem with this. I need to use a newer version of the commons-httpclient.jar and when I include it in <jboss home>/server/default/lib and deploy my EJB, I get a java.lang.VerifyError. I asusme this is because the version in <jboss home>/lib is already loaded.

JBoss 3.2.1 and trying to use commons-httpsclient-2.0.jar

Any ideas?

[triathlon98]

Try replacing the file in <jboss home>/lib

Joachim

[treespace]

Put the jars you need in your EAR base and add it to the manifest of the jar that uses it. That will be used before the JBoss folder jars. Same idea with web-app where the WEB-INF/lib folder will override anything in the EAR or in the container or in the system classpath.

[jdbrown]

Thanks. I replaced the <jboss home>/lib with the latest version and it works fine now.