[infinispan-issues] [JBoss JIRA] (ISPN-3596) LifecycleManager of query module should use the Provider mechanism instead of relying on brute class loading

[Adrian Nistor (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Nistor updated ISPN-3596:
--------------------------------

    Fix Version/s: 6.0.0.Final

    
> LifecycleManager of query module should use the Provider mechanism instead of relying on brute class loading
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-3596
>                 URL: https://issues.jboss.org/browse/ISPN-3596
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Querying
>    Affects Versions: 6.0.0.CR1
>            Reporter: Adrian Nistor
>            Assignee: Adrian Nistor
>             Fix For: 6.0.0.Final
>
>
> This is used to customize the SearchFactory programmatic mappings only if remote query module is present in classpath.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira