Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Wed, 15 Jan 2014 11:13:20 +0000 (UTC)
From: "Oleg Kalnichevski (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.12688962.1389775043918.5460.1389784400451@arcas>
In-Reply-To: <JIRA.12688962.1389775043918@arcas>
References: <JIRA.12688962.1389775043918@arcas>
Subject: [jira] [Commented] (HTTPASYNC-65) HttpAsyncClient does not work in
 OSGi
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HTTPASYNC-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871938#comment-13871938 ] 

Oleg Kalnichevski commented on HTTPASYNC-65:
--------------------------------------------

Christian,
I understand that things can be thrown together into one big pile with a whole bunch optional dependencies one would have to be careful enough to not refer unintentionally but I see little sense in doing so. Not everything in this world has to be OSGi enabled. At least in my opinion. 

Can we keep the separate module and just fix those things that prevent you from using it with CXF?

Oleg

> HttpAsyncClient does not work in OSGi
> -------------------------------------
>
>                 Key: HTTPASYNC-65
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-65
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Bug
>    Affects Versions: 4.0 Final
>            Reporter: Christian Schneider
>             Fix For: 4.0.1
>
>         Attachments: HTTPASYNC-65-1.patch
>
>
> We are using the http async client for CXF. In the current trunk we reference the 4.0 version. 
> Unfortunately the bundle does not work for us. I spotted two problems:
> 1. The Bundle-SymbolicName is the same as the one in httpclient
> In the pom there is:
> <Bundle-SymbolicName>${project.groupId}.httpclient</Bundle-SymbolicName>
> See http://search.maven.org/remotecontent?filepath=org/apache/httpcomponents/httpasyncclient-osgi/4.0/httpasyncclient-osgi-4.0.pom
> 2. The bundle refers to commons logging api 1.1.3 but pax logging only provides 1.0.4. I will also try to fix this for pax logging. 
> I think it should be possible to open up the import range for pax logging so you also accept the 1.0.x version.
> I checked out the current trunk and was able to make it work by doing some changes in the poms.
> I found that httpasyncclient has separate projects for the normal jar and the OSGi jar. Is this really necessary? I was able to switch the normal jar to packaging bundle and configure it there. This has the advantage that people only have to use one maven artifact for OSGi and non OSGi usage. This is espacially intersting for frameworks like cxf that live in both worlds.
> I will provide a patch with my changes. So you can review what I did.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org