M. le Rutte

I don't have the structure of Jackess in my head to be able to conclude that to be honest. As far as my OSGi knowledge goes the crypto bundle is best off as a fragment to the orignal bundle, as, like I wrote before, there is no need to run the crypto bundle on its own. In that case it will share a classloader, yet the consuming package must be able to access the class. If it can access the CryptCodecUtil then I guess it may work. Just a small checkup, will it run in Java 9's modular classpath? It...

I don't have the structure of Jackess in my head to be able to conclude that to be honest. As far as my OSGi knowledge goes the crypto bundle is best off as a fragment to the orignal bundle, as, like I wrote before, there is no need to run the crypto bundle on its own. In that case it will share a classloader, yet the consuming package must be able to access the class. If it can access the CryptCodecUtil then I guess it may work. Just a small checkup, will it run in Java 9's modular classpath? It...

Just noted your update, I guess it would not work as the CryptCodecProvider still would not be visible to the classloader of the bundle. In OSGi each bundle gets its own classloader and that classloader can only access public (exported) classes of another bundle. Whereas in 'plain' Java jars the entire path becomes a single namespace and multiple jars contributing to the same package become merged, this doesn't happen in OSGi,

It appears that I was wrong, the problem is remains that the crypt provider does not have its own namespace. I made the encrypt bundle a fragment bundle by adding the header Fragment-Host: com.healthmarketscience.jackcess;bundle-version="[2.1.6,3)", and the kept the Export-Package header. Additionally I exported the .impl package from the regular Jackcess bundle. Unfortunately this doesn't make the CryptCodecProvider visible to my OSGi bundle, which is thus not capable of instantiating the Crypt...

Both. The crypto package should either be moved to a separate package, but more optimally...

Besides having to add the .impl as Export-Package, the crypto implementation itself...

The database itself is not password protected, but the database is encrypted. Without...

The database itself is not password protected, but the database is encrypted. Without...