>>>>> Steinar Bang <s...@dod.no>: > I opened a Jira on Apache Aries spi fly for this: > https://issues.apache.org/jira/browse/ARIES-2110
Though I myself is probably to blame for the use of the Dynamic Weaving Bundle. Before I load anything in karaf, it has the following Aries bundles: karaf@root()> bundle:list -t 10 | grep -i aries 23 │ Active │ 30 │ 1.1.5 │ Apache Aries JMX API 24 │ Active │ 30 │ 1.1.8 │ Apache Aries JMX Core 25 │ Active │ 30 │ 1.2.0 │ Apache Aries Whiteboard support for JMX DynamicMBean services 26 │ Active │ 20 │ 1.1.3 │ Apache Aries Util karaf@root()> Then I load my application: karaf@root()> feature:repo-add mvn:no.priv.bang.oldalbum/karaf/LATEST/xml/features Adding feature url mvn:no.priv.bang.oldalbum/karaf/LATEST/xml/features karaf@root()> feature:install oldalbum-with-derby karaf@root()> And after that, the following Aries bundles are loaded karaf@root()> bundle:list -t 10 | grep -i aries 23 │ Active │ 30 │ 1.1.5 │ Apache Aries JMX API 24 │ Active │ 30 │ 1.1.8 │ Apache Aries JMX Core 25 │ Active │ 30 │ 1.2.0 │ Apache Aries Whiteboard support for JMX DynamicMBean services 26 │ Active │ 20 │ 1.1.3 │ Apache Aries Util 109 │ Active │ 20 │ 1.1.13 │ Apache Aries Proxy Service 110 │ Active │ 40 │ 1.3.4 │ Apache Aries SPI Fly Dynamic Weaving Bundle karaf@root()> And bundle 109 and 110 are caused by my liquibase karaf feature: https://github.com/steinarb/liquibase-karaf-feature/blob/master/liquibase-core-karaf/src/main/feature/feature.xml#L17 Whether the dynamic weaving bundle is necessary for the liquibase feature, or if it can use the static SPI Fly bundle, I have no idea. But I can try, I guess...? (I still don't know what dynamic weaving does, why dynamic weaving is connected to the service loader, and even less why the dynamic weaving code insists that my bean AlbumEntry and the JDBC ResultSet should have a common ancestor...)
