]
Dan Berindei resolved ISPN-2489.
--------------------------------
Resolution: Done
I believe this was fixed by ISPN-3850, using an exact classloader.
infinispan-core stores resources in default package, preventing OSGI
export
---------------------------------------------------------------------------
Key: ISPN-2489
URL:
https://issues.jboss.org/browse/ISPN-2489
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 5.1.6.FINAL, 5.2.0.Beta3
Reporter: Vitalii Tymchyshyn
Currently infinispan stores resources (e.g. infinispan-core-component-metadata.dat) in
the default package. This makes this resources private to infinispan-core OSGI bundle as
default package can't be exported
So, first of all it does not start by default when cache manager is created from another
bundle. If configuration is created explicitly passing infinispan-core classloader, it can
start, but no additional components can be used (e.g. loaders from another bundles).
I can see next possible options to handle this:
1) Move resources to the package
2) Use multiple classloaders to read resources (as it's done for classes)
3) Use exact classloader, e.g. use fixed infinispan-core classloader to get
infinispan-core-component-metadata.dat. Dunno if this would work for all resources, like
jgroups configuration files.