Tomcat, HttpClient, and JBoss 3.2.1

[stevecoh2]

commons-httpclient.jar is included with jboss in the {jboss.root}/lib directory of a jboss installation. I believe that this is needed by Tomcat, which explains why JBoss puts it so high in the hierarchy.

This can present classloader problems if the application has need of a higher version of httpclient than the version that came with JBoss.

I am in a situation where I am forced to use JBoss 3.2.1 but client code needs HttpClient-2.0. JBoss 3.2.1 ships with HttpClient 1.0.16. I'd rather avoid any classloader isolation strategies if possible. Does anyone know if HttpClient is stable and backward-compatible enough so as to allow the HttpClient jar that came with JBoss 3.2.1 (1.0.16) to be replaced by a 2.0.x version without messing Tomcat up?

[stevecoh2]

I see people reading this thread but can someone please ANSWER? This is a serious problem and I need some guidance.

I need
1) assurance, if someone can give it to me, that replacing HttpClient in JBoss 3.2.1 with a more recent version is possible or assurance that it won't work

OR

2) more information on how to get the newer version of HttpClient to load within my application without affecting the entire classloading scheme of JBoss. The JBoss wiki docs on this are insufficient for this purpose.

Can't someone offer some assistance here? Thanks.

[darranl]

"stevecoh2" wrote:
I see people reading this thread but can someone please ANSWER?

And how many posts have you answered recently?

[stevecoh2]

I answer posts in areas where I have expertise. JBoss is not one of my strong areas. This is an area where I need the expertise of others. I would expect someome from the JBoss team to be able to provide an answer here.