Hi Eric, Yes, 3.x and 4.0 can easily coexist within the same classloader. Because they use different package names:
3.x: org.apache.commons.httpclient 4.0: org.apache.http Cheers, Ortwin Hubert, Eric wrote: > Hi devs, > > from time to time I'm following the list and read a lot of posts where Oleg > mentioned that 3.1 has entered a kind of end of life phase and all users are > strongly encouraged to switch to 4.0. > According to my understanding and as the major version change indicates 4.0 > involves incompatible API changes. In fact as far as I know it was a major > rewrite. > > The interesting question which obviously popped up was: How to > update/migrate? I'm not worried about our own code using HttpClient 3.1 API. > We would need to invest some time to change our code to make use of the new > API and are done. I'm much more concerned about the great number of third > party libraries we are using depending on HttpClient 3.1, where we have no > influence on. So the next more or less obvious question is: Are the rewrites > that "drastic" (also in terms of package and class renaming) that HttpClient > 3.1 and HttpClient 4.0 are two distinct set of classes which can happily > coexist in the same class loader? > > > Regards, > Eric -- [web] http://www.odi.ch/ [blog] http://www.odi.ch/weblog/ [pgp] key 0x81CF3416 finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
