Really, has no one had this problem before? We are in a situation where we do not control the version of jboss that is in deployment, so we are stuck with 3.2.1. Yet we need to add application functionality that requires HttpClient 2.0, while JBoss 3.2.1 ships with 1.0.x.
By placing commons-httpclient.jar in /lib instead of /server/lib, JBoss makes it nearly impossible for applications to upgrade this libarary if they need it. Can someone please tell me 1) whether it is possible to package a later version of HttpClient with my application and have it work without conflicts? I've looked at the wiki about classloader isolation but I don't completely understand it. Are you supposed to replace "unique-archive-name" with a unique archive name - and if so, where does this unique archive have to reside? OR 2) Would it just be simpler to replace the commons-httpclient.jar in the /lib directory with the newer one and would that cause any problems for jboss and/or tomcat? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897349#3897349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897349 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
