[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) jira-events at lists.jboss.org
Mon Oct 7 07:26:02 EDT 2013


    [ https://issues.jboss.org/browse/ISPN-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12810432#comment-12810432 ] 

Adrian Nistor commented on ISPN-3596:
-------------------------------------

Need to test this against server too.
                
> 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
>
> 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


More information about the infinispan-issues mailing list