>>>>> Steinar Bang <[email protected]>: >> What I was trying to tell you, is that by replacing your >> spifly-feature with the aries-proxy-feature and a single spifly >> bundle, the classloading issue might be fixed. Liquibase is able to >> find the Default Log Service, as far as I can see.
> Ahhh! I see! >> I got 2 new exceptions, one of which can be ignored.If you manage to >> fix the other exception, I think you get a little closer to the >> solution. > Thanks! I will try! I'll report back in this (long) thread! I didn't get any exceptions from liquibase pro, but I got 3 exceptions "No Common Superclass:javax/crypto/SecretKey javax/crypto/SecretKeyFactory": https://gist.github.com/steinarb/3c3ff4e570bf8c6a380343233ed1e471#file-karaf-log-L342 "liquibase.parser.core.xml.XSDLookUpException: Unable to resolve xml entity http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd locally: liquibase.secureParsing is set to 'true' which does not allow remote lookups. Set it to 'false' to allow remote lookups of xsd files." https://gist.github.com/steinarb/3c3ff4e570bf8c6a380343233ed1e471#file-karaf-log-L439 (this one is possible fixable by disabling XSD validation...?) java.lang.NullPointerException https://gist.github.com/steinarb/3c3ff4e570bf8c6a380343233ed1e471#file-karaf-log-L535 (possibly caused by ServiceLoader not finding any services...? But that is guessing on my part) Here's the feature.xml used https://gist.github.com/steinarb/22f4ea2e7eda7018bae0af2ad7f774df Hm... I removed the liquibase-slf4j bundle from the feature.xml and then I got a different karaf.log https://gist.github.com/steinarb/c04967029621509053f0b6c5903f5fcf Not the "normal" error messages (e.g. "Cannot find default Log service"), but error messages from the derby shutdown, and no logging indicating that liquibase is actually doing anything. Hm... I tried again, and this time it looks like liquibase failing because the derby database has been shut down...? https://gist.github.com/steinarb/fe342779dfe50b82345e9ac04718f17d#file-karaf-log-L484 And this time I again got the "No Common Superclass:javax/crypto/SecretKey javax/crypto/SecretKeyFactory" error. So the behaviour isn't entirely predictable with this setup...?
