>>>>> Steinar Bang <s...@dod.no>: > When I pull in Apache Aries spifly on one of my bundles I get a weird > error in karaf.log: > java.lang.RuntimeException: No Common > Superclass:no/priv/bang/oldalbum/services/bean/AlbumEntry java/sql/ResultSet
> Here's the error: > > https://gist.github.com/steinarb/4fc4b86c49cbdb151d8b9e626366ff07#file-karaf-log-L790 > There is nothing in my code that tries to unify AlbumEntry or ResultSet. > But there is a method that unpacks a row in a ResultSet into an albumentry: > > https://github.com/steinarb/oldalbum/blob/master/oldalbum.backend/src/main/java/no/priv/bang/oldalbum/backend/OldAlbumServiceProvider.java#L819 > Is that method the cause of the misunderstanding? > Is there a way to tell spifly not to look at any classes in my bundle? > If not, is there a way to make spifly disregard these particular > classes? > What I'm trying to do is to load SPI plugins from other bundles > (TwelveMonkeys image IO plugins) so that they become available to my > bundle's code. >From the stack trace it looks like I'm using dynamic weaving? https://aries.apache.org/documentation/modules/spi-fly.html Is dynamic weaving something I need or want if I want to have SPI classes work in an OSGi context? Note that I'm already using Apache Aries SPI Fly to make Liquibase work, so I'm bound by whatever Liquibase requires.
