camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Savas Ali Tokmen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1862) camel-cxf bundle doesn't specify any Import-Package version
Date Thu, 30 Jul 2009 13:52:35 GMT

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

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

Hello

I've applied the patch on the CAMEL-CXF 2.0-M3 tag, and retried launching the platform with
various versions of CXF. The behavior is as follows:

 - When only CXF 2.2.2 is present, all my tests pass (i.e., no regression)
 - When only CXF 2.0.11 is present, the bundle does not resolve but (as expected) says things
like: Unresolved constraint in bundle 132: package; (&(package=org.apache.cxf.headers)(version>=2.2.0)(!(version>=3.0.0)))
 - When both CXF 2.0.11 and 2.2.2 are present, the bundle does resolve and when started seems
to take the good version

This bug can therefore be marked "closed, fixed".

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
>             Fix For: 1.6.2, 2.0.0
>
>
> 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.


Mime
View raw message