camel-karaf 4.8.2: broken JAXBContext

[ivan-ra]

this code causes ClassNotFoundException (org.glassfish.jaxb.runtime.v2.ContextFactory not found) for routes deployed on karaf environment (works well in standalone routes):

import jakarta.xml.bind.JAXBContext;
...
JAXBContext ctx = JAXBContext.newInstance(ArrayList.class);

because camel-karaf has 2 incompatible features jaxb-runtime, and loads only 3.0.2 jaxb bundles:

    <feature name="jaxb-runtime" version="3.0.2">
        <feature version="[3,4)">jakarta-xml-bind</feature>
        <bundle dependency="true">mvn:com.sun.xml.bind/jaxb-core/3.0.2</bundle>
        <bundle dependency="true">mvn:com.sun.xml.bind/jaxb-impl/3.0.2</bundle>
        <bundle dependency="true">mvn:com.sun.xml.bind/jaxb-osgi/3.0.2</bundle>
    </feature>
    <feature name="jaxb-runtime" version="4.0.5">
        <feature version="[4,5)">jakarta-xml-bind</feature>
        <bundle dependency="true">mvn:com.sun.istack/istack-commons-runtime/4.1.2</bundle>
        <bundle dependency="true">mvn:org.glassfish.jaxb/jaxb-core/4.0.5</bundle>
        <bundle dependency="true">mvn:org.glassfish.jaxb/jaxb-runtime/4.0.5</bundle>
        <bundle>mvn:org.glassfish.hk2/osgi-resource-locator/2.5.0-b42</bundle>
    </feature>

karaf@root()> feature:list|grep jaxb-runtime
jaxb-runtime                             | 3.0.2            |          | Uninstalled | camel-4.8.2                       |
jaxb-runtime                             | 4.0.5            |          | Started     | camel-4.8.2                       |

and loads only packages v 3.0.2:

karaf@root()> list|grep JAXB
113 | Active |  50 | 4.8.2              | Apache Camel :: Karaf :: Core :: XML JAXB
131 | Active |  80 | 3.0.2              | JAXB OSGI
karaf@root()> package:exports -p org.glassfish.jaxb.runtime.v2
Package Name                                       | Version | ID  | Bundle Name
---------------------------------------------------+---------+-----+---------------------------
org.glassfish.jaxb.runtime.v2.model.annotation     | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.model.impl           | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.model.runtime        | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.runtime.output       | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.runtime.property     | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.runtime.reflect.opt  | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.runtime.reflect      | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.runtime.unmarshaller | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.runtime              | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.schemagen.xmlschema  | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.schemagen            | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2.util                 | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi
org.glassfish.jaxb.runtime.v2                      | 3.0.2   | 131 | com.sun.xml.bind.jaxb-osgi

I have tried to change 4.0.5 bundle dependency value to "false", but it does not work because camel-blueprint requires jaxb bundles version 3.

[ivan-ra]

I think camel-blueprint needs to exclude jaxb3 dependencies (com.sun.xml.fastinfoset.* packages) and use jaxb v4*

[ivan-ra]

please remove unused imports from camel-blueprint manifest!
I removed this packages: com.sun.xml.* , org.jvnet.* from manifest, changed axb-runtime feature (dependency="false"), and now all works well (except camel-cxf, I think there are some unused imports too)

    <feature name="jaxb-runtime" version="4.0.5">
        <feature version="[4,5)">jakarta-xml-bind</feature>
        <bundle dependency="true">mvn:com.sun.istack/istack-commons-runtime/4.1.2</bundle>
        <bundle dependency="false">mvn:org.glassfish.jaxb/jaxb-core/4.0.5</bundle>
        <bundle dependency="false">mvn:org.glassfish.jaxb/jaxb-runtime/4.0.5</bundle>
        <bundle>mvn:org.glassfish.hk2/osgi-resource-locator/2.5.0-b42</bundle>
    </feature>

[essobedo]

Hi, thx for the ticket. If you don't mind, let's focus first on the problem before focusing on the solution knowing that the 2 versions of the feature were proposed for good reasons. So please provide steps to reproduce your issue with a simple camel route and/or propose a PR with a test case.

[jbonofre]

Thanks for the report. Do you have a simple reproducer ?

[ivan-ra]

in any route/bundle just add this code and try to install it:

JAXBContext ctx = JAXBContext.newInstance(ArrayList.class); //any class here

(bundle should use camel feature)

More precisely, route/bundle must use camel-blueprint (this requires jaxb v3) and contain java code like this (this requires jaxb v4):

JAXBContext ctx = JAXBContext.newInstance();

[ivan-ra]

for me works this solution:

• exclude unused imports from camel-blueprint manifest ( com.sun.xml.* , org.jvnet.* )
• change both jaxb-runtime features like this

    <feature name="jaxb-runtime" version="3.0.2">
        <feature version="[3,4)">jakarta-xml-bind</feature>
        <bundle dependency="false">mvn:com.sun.xml.bind/jaxb-core/3.0.2</bundle>
        <bundle dependency="false">mvn:com.sun.xml.bind/jaxb-impl/3.0.2</bundle>
        <bundle dependency="false">mvn:com.sun.xml.bind/jaxb-osgi/3.0.2</bundle>
    </feature>
    <feature name="jaxb-runtime" version="4.0.5">
        <feature version="[4,5)">jakarta-xml-bind</feature>
        <bundle dependency="true">mvn:com.sun.istack/istack-commons-runtime/4.1.2</bundle>
        <bundle dependency="false">mvn:org.glassfish.jaxb/jaxb-core/4.0.5</bundle>
        <bundle dependency="false">mvn:org.glassfish.jaxb/jaxb-runtime/4.0.5</bundle>
        <bundle>mvn:org.glassfish.hk2/osgi-resource-locator/2.5.0-b42</bundle>
    </feature>

after this route works well and camel-cxf starts too

karaf@root()> feature:list|grep jaxb-runtime
jaxb-runtime                             | 3.0.2            |          | Started     | camel-4.8.2                       |
jaxb-runtime                             | 4.0.5            |          | Started     | camel-4.8.2                       |
karaf@root()> list|grep JAXB
110 | Active |  50 | 4.8.2              | Apache Camel :: Karaf :: Core :: XML JAXB
128 | Active |  80 | 3.0.2              | Old JAXB Core
129 | Active |  80 | 3.0.2              | Old JAXB Runtime
130 | Active |  80 | 3.0.2              | JAXB OSGI
308 | Active |  80 | 4.0.5              | JAXB Core
309 | Active |  80 | 4.0.5              | JAXB Runtime

[ivan-ra]

Cant reproduce it with online karaf/project tests. It loads both jaxb runtime versions.
But for intranet projects I've made offline assembly with karaf-maven-plugin, and for some reason it loads only jaxb-osgi 3.0.2.
I don't know if this will be fixed, but at least there are extra imports to be deleted from camel-blueprint manifest (!com.sun.xml.*,!org.jvnet.*, in pom.xml). This packages from jaxb 3.0.2, but camel-blueprint uses jaxb runtime 4.0.5.

For offline karaf my solution is:

• exclude unused imports from camel-blueprint manifest (!com.sun.xml.*,!org.jvnet.*, in pom.xml)

        <camel.osgi.import>
            jakarta.xml.bind*;version="[3,5)",!com.sun.xml.*,!org.jvnet.*,
            *
        </camel.osgi.import>

• fix both jaxb-runtime features (remove dependency="true" attribute). This jaxb bundles exports the same packages, but different versions. So, we cant use optional dependency, but only exact:

    <feature name="jaxb-runtime" version="${jaxb3-core-version}">
        <feature version="[3,4)">jakarta-xml-bind</feature>
        <bundle>mvn:com.sun.xml.bind/jaxb-core/${jaxb3-core-version}</bundle>
        <bundle>mvn:com.sun.xml.bind/jaxb-impl/${jaxb3-impl-version}</bundle>
        <bundle>mvn:com.sun.xml.bind/jaxb-osgi/${jaxb3-osgi-version}</bundle>
    </feature>

    <feature name="jaxb-runtime" version="${jaxb-core-version}">
        <feature version="[4,5)">jakarta-xml-bind</feature>
        <bundle dependency="true">mvn:com.sun.istack/istack-commons-runtime/${auto-detect-version}</bundle>
        <bundle>mvn:org.glassfish.jaxb/jaxb-core/${glassfish-jaxb-runtime-version}</bundle>
        <bundle>mvn:org.glassfish.jaxb/jaxb-runtime/${glassfish-jaxb-runtime-version}</bundle>
        <bundle>mvn:org.glassfish.hk2/osgi-resource-locator/${osgi-resource-locator-version}</bundle>
    </feature>

tested for 4.8.x branch

[jbonofre]

@ivan-ra do you have your local m2 repo or Karaf system repo populated with all artifacts ?

[ivan-ra]

yes, there are all needed bundles in system repo.
I looked at the assembly and finally found cause. And I can reproduce it even on online karaf.
This steps on new clean karaf:

        __ __                  ____
       / //_/____ __________ _/ __/
      / ,<  / __ `/ ___/ __ `/ /_
     / /| |/ /_/ / /  / /_/ / __/
    /_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.4.7)

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.

karaf@root()> feature:repo-add camel 4.8.5
Adding feature url mvn:org.apache.camel.karaf/apache-camel/4.8.5/xml/features
karaf@root()> feature:install camel
karaf@root()> list|grep JAXB
100 | Active |  50 | 4.8.5   | Apache Camel :: Karaf :: Core :: XML JAXB
106 | Active |  80 | 3.0.2   | Old JAXB Core
107 | Active |  80 | 3.0.2   | JAXB OSGI
122 | Active |  80 | 4.0.5   | JAXB Core
123 | Active |  80 | 4.0.5   | JAXB Runtime

• Both versions of bundles loaded properly
• And now I install activemq-client:

karaf@root()> feature:repo-add activemq 6.1.5
Adding feature url mvn:org.apache.activemq/activemq-karaf/6.1.5/xml/features
karaf@root()> feature:install activemq-client
karaf@root()> list|grep JAXB
100 | Active |  50 | 4.8.5   | Apache Camel :: Karaf :: Core :: XML JAXB
107 | Active |  80 | 3.0.2   | JAXB OSGI

• As you can see 4.0.5 bundles gone, only JAXB OSGI left

[jbonofre]

@ivan-ra thanks for sharing. I think it could be a conflict with activemq-client feature. Let me double check there.

[jbonofre]

It should now be OK with ActiveMQ 6.2.x as it's now aligned with JAXB 4.x version.