Hi Roland, As the provider of the original bundling descriptor, I have to admit, that I was not aware of this issue ....
You also say, that HTTPClient is not built to be used as a shared library. Can you elaborate on that a bit, please ? The reason for me asking is that we exactly do that, and if there is actually an issue there, I would like to be prepared (or prevent it altogether): Thanks alot. Consequently, if there is a problem, we might (a) provide an activator which "shutdownAll()" on bundle stop [I could do that] or (b) remove HTTPClient again. Regards Felix On 2/22/07, Roland Weber <[EMAIL PROTECTED]> wrote:
Hello Enrique, > A wrapper POM creating an OSGi bundle of the 3rd-party library was committed on rev 510316. > > URL: http://svn.apache.org/viewvc?view=rev&rev=510316 > >> commons-httpclient 3.0.1 wrapping >> --------------------------------- >> >> Key: FELIX-212 >> URL: https://issues.apache.org/jira/browse/FELIX-212 >> >> Create an OSGi bundle for the commons-httpclient 3.0.1 jar. > I just wanted to point out that in HttpClient 3 (and 2), the class MultiThreadedHttpConnectionManager starts background threads when used. If I am not mistaken, the OSGi bundle mechanism expects bundles to clean up when they are stopped. In order to clean up, you would need a bundle activator that calls MultiThreadedHttpConnectionManager.shutdownAll(); when the bundle is stopped. http://jakarta.apache.org/commons/httpclient/apidocs/org/apache/commons/httpclient/MultiThreadedHttpConnectionManager.html#shutdownAll() cheers, Roland
