[jira] Commented: (CAMEL-1862) camel-cxf bundle doesn't specify any Import-Package version

["Savas Ali Tokmen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53036#action_53036 ] 

Savas Ali Tokmen commented on CAMEL-1862:
-----------------------------------------

Hello

Looks like http://svn.apache.org/viewvc/camel/trunk/components/camel-cxf/pom.xml?view=diff&r1=799251&r2=799252&pathrev=799252 fixes this :)

Cheers

S. Ali Tokmen
http://ali.tokmen.com/

> camel-cxf bundle doesn't specify any Import-Package version
> -----------------------------------------------------------
>
>                 Key: CAMEL-1862
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1862
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.0-M3
>         Environment: CAMEL, CXF, OSGi Felix
>            Reporter: Savas Ali Tokmen
>            Assignee: Willem Jiang
>
> The camel-cxf component is currently generated against CXF version 2.2.2.
> As a result, the camel-cxf module as well as the camel-cxf bundle require CXF 2.2. More importantly, that bundle does not work correctly with CXF 2.0 (note that this is an expected behavior, CXF has had API changes with its 2.2 version).
> Now, the trouble is that the camel-cxf JAR's MANIFEST has an Import-Package on org.apache.cxf.* components without specifying any version! As a result, when it looks for CXF and both CXF 2.0 and 2.2 are present on the platform, it sometimes chooses the wrong one.
> To solve this issue, version specifiers should be added to the Import-Package declarations of the camel-cxf bundle. I guess an import on version 2.2 would be enough (we don't need to specify 2.2.2 explicitely).
> Cheers
> S. Ali Tokmen
> http://ali.tokmen.com/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.