[
https://issues.apache.org/activemq/browse/CAMEL-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eoghan Glynn updated CAMEL-2442:
--------------------------------
Description:
There's a mismatch between the explicit version constraints on the
javax.activation, javax.annotation, javax.jws, javax.xml.ws etc. packages in
the camel-cxf manifest and the actual version assigned to these packages by
Equinox when pulled in via the system packages from the Java6 rt.jar.
This causes bundle resolution failures such as the following:
{code}
org.osgi.framework.BundleException: The bundle could not be resolved. Reason:
Package uses conflict: Import-Package: org.apache.camel; version="2.2.something"
{code}
Normally this issue could be suppressed by configuring the Equinox system
packages to exclude the problematic javax.* packages. However, we don't have
enough control over this in pax-runner 1.3 (which unilaterally adds these
packages in the generated config.ini).
The solution is to loosen the version constraints on these imports in the
camel-cxf bundle manifest.
was:
There's a mismatch between the explicit version constraints on the
javax.activation, javax.annotation, javax.jws, javax.xml.ws etc. packages in
the camel-cxf manifest and the actual version assigned to these packages by
Equinox when pulled in via the system packages from the Java6 rt.jar.
This causes bundle resolution failures such as the following:
{code}
org.osgi.framework.BundleException: The bundle could not be resolved. Reason:
Package uses conflict: Import-Package: org.apache.camel;
version="2.2.99.0-fuse-SNAPSHOT"
{code}
Normally this issue could be suppressed by configuring the Equinox system
packages to exclude the problematic javax.* packages. However, we don't have
enough control over this in pax-runner 1.3 (which unilaterally adds these
packages in the generated config.ini).
The solution is to loosen the version constraints on these imports in the
camel-cxf bundle manifest.
> Explicit version ranges on javax.* imports in camel-cxf bundle manifest cause
> a problem when running on equinox via pax-runner
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-2442
> URL: https://issues.apache.org/activemq/browse/CAMEL-2442
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.1.0
> Environment: $ java -version
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) Server VM (build 14.2-b01, mixed mode)
> $ uname -a
> Linux geodesic 2.6.28-17-generic #58-Ubuntu SMP Tue Dec 1 18:57:07 UTC 2009
> i686 GNU/Linux
> Reporter: Eoghan Glynn
> Fix For: 2.2.0
>
> Attachments: camel-2442.patch
>
>
> There's a mismatch between the explicit version constraints on the
> javax.activation, javax.annotation, javax.jws, javax.xml.ws etc. packages in
> the camel-cxf manifest and the actual version assigned to these packages by
> Equinox when pulled in via the system packages from the Java6 rt.jar.
> This causes bundle resolution failures such as the following:
> {code}
> org.osgi.framework.BundleException: The bundle could not be resolved. Reason:
> Package uses conflict: Import-Package: org.apache.camel;
> version="2.2.something"
> {code}
> Normally this issue could be suppressed by configuring the Equinox system
> packages to exclude the problematic javax.* packages. However, we don't have
> enough control over this in pax-runner 1.3 (which unilaterally adds these
> packages in the generated config.ini).
> The solution is to loosen the version constraints on these imports in the
> camel-cxf bundle manifest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
