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

IndexingConfigurationBuilder query module validation is wrong

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.0.0.Beta2
    • 7.0.0.Beta1
    • Configuration
    • None

      The query module is ultimately loaded by the ComponentRegistry, which will load its modules via the classloader returned by GlobalConfiguration.classLoader(). However, the logic in IndexingConfigurationBuilder.validate(...) tests that the query module classes are accessible from the classloader that loaded the IndexingConfigurationBuilder itself.

      In WildFly, to use querying, one would use the following configuration:
      <cache-container module="org.infinispan.query"/>
      Internally, this configures Infinispan's GlobalConfiguration with the classloader of the "org.infinispan.query" module.
      However, the IndexingConfigurationBuilder class is contained in the "org.infinispan" - which does not depend on the "org.infinispan.query" module. Consequently, IndexingConfigurationBuilder validation fails, even though the module would have been successfully loaded at runtime.

              wburns@redhat.com Will Burns
              pferraro@redhat.com Paul Ferraro
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: