Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-2489

infinispan-core stores resources in default package, preventing OSGI export

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Done
    • 5.1.6.FINAL, 5.2.0.Beta3
    • None
    • Core
    • None
    • Workaround Exists
    • Hide

      My current workaround it to create a fragment bundle that connects to infinispan-core and imports all needed component bundles

      Show
      My current workaround it to create a fragment bundle that connects to infinispan-core and imports all needed component bundles

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tivv00_jira Vitalii Tymchyshyn (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: