[infinispan-issues] [JBoss JIRA] (ISPN-1224) Make sure a Lucene Directory can be configured in the general AS configuration independently from the Lucene version

[Sanne Grinovero (Commented) (JIRA)]

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

Sanne Grinovero commented on ISPN-1224:
---------------------------------------

After some thoughts, I don't think this is a good idea; the Lucene Directory is already compatible with multiple Lucene versions, the problem here is with the (optional) Key2String usage and CacheLoaders, in which someone might want to use multiple versions of the same class.

The only way to properly isolate these from an AS using them is to start your own Infinispan instance; what people should try to reuse is actually the JGroups channel from the AS, not the CacheManager. With AS7 the JGroups channel is "muxed" and the existing channel can be borrowed to efficiently start multiple caches on top of the same channel, hence providing full isolation and multiple versions wouldn't be a problem.
                
> Make sure a Lucene Directory can be configured in the general AS configuration independently from the Lucene version
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-1224
>                 URL: https://issues.jboss.org/browse/ISPN-1224
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Lucene Directory
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>            Priority: Minor
>
> As discussed on forums: http://community.jboss.org/message/612561
> and mailing list: http://infinispan.markmail.org/thread/hixrdqas4jn5cuok
> configuring such a cache needs Externalizers and optionally Key2String transformers which are bundled in the infinispan-lucene-directory module, but since this module depends on Lucene people would rather want to avoid having to move this jar to the commons lib path of the application server, but still want to configure the cache in the AS configuration to not have to start a second CacheManager.
> This issue would not apply anymore if support asymmetric clusters is implemented

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira