Eric, The intention is to keep HttpClient 3.0 compile-compatible with HttpClient 2.x (except for all that ugly stuff that has been deprecated in 2.0). Feel free to submit a patch for the HttpException class.
Keep us posted on the progress Cheers, Oleg On Wed, 2004-09-29 at 21:10, Eric Johnson wrote: > Some feedback, finally. > > I attempted to compile the "client" tools of the slide project with the > HttpClient 3.0 alpha release. > > You'll probably not be surprised to hear that it didn't compile. It > turns out that a few missing functions in the HttpException class cause > the compile failures. I added those few functions in to my local copy, > and everything compiled. > > The code that I have that runs on top of those libraries also compiled > without any further changes. > > I didn't actually run any of the code, though. I suspect that the > changes in exception handling would make any such endeavors more work > than I want to tackle right now. > > I think my next step is to ask that the client libraries of the Slide > project start using different version numbers from the server side > tools, and then suggest a 3.0 release of the slide client libraries that > will use the 3.0 HttpClient. Since getting it to compile was easy, I > suspect that the rest of it will be fairly straightforward too. > > -Eric. > > Oleg Kalnichevski wrote: > > >As far as I know the following projects rely on HttpClient 2.0 as a > >required or optional dependency > > > >* Apache Jakarta Slide (http://jakarta.apache.org/slide/) > >* Apache Jakarta Cactus (http://jakarta.apache.org/cactus/) > >* Apache Axis (http://ws.apache.org/axis/) > >* Apache XML-RPC (http://ws.apache.org/xmlrpc/) > >* Spring Framework (http://www.springframework.org/) > >* HtmlUntit (http://htmlunit.sourceforge.net/) > >* XINS (http://xins.sourceforge.net/) > > > >I just wonder if any of the projects' committers are currently > >subscribed to or monitor this mail list? > > > >We would love to know if there are any plans to evaluate HttpClient 3.0, > >or any migration plans already. What can we do to make the transition, > >if planned, easier? > > > >Oleg > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]