[infinispan-issues] [JBoss JIRA] (ISPN-1414) Introduce a builder than can create an Infinispan CacheManager

[Galder Zamarreño (Commented) (JIRA)]

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

Galder Zamarreño commented on ISPN-1414:
----------------------------------------

Another important aspect of this is shutdown of a cache manager. Currently a cache manager shutdown the executors it creates, even if they come from an app server. So, if we're gonna have a builder that allows an app server to pass components to a cache manager so that a deployment can have its own cache manager, then we need to address what a cache manager shuts down when stopping. Otherwise, when a deployment goes down and shuts down the cache manager, it would shut down all cache managers' executors, not good!


                
> Introduce a builder than can create an Infinispan CacheManager
> --------------------------------------------------------------
>
>                 Key: ISPN-1414
>                 URL: https://issues.jboss.org/browse/ISPN-1414
>             Project: Infinispan
>          Issue Type: Feature Request
>            Reporter: Pete Muir
>            Assignee: Manik Surtani
>             Fix For: 6.0.0.FINAL
>
>
> Provide a builder class that allows passing in of SPI instances, rather than doing lookup. This allows for much easier integration, as context from the app server bootstrap can be easily passed in.
> For example:
> {code}
> public class CacheManagerBuilder  {
>    void setClassLoader(ClassLoader cl);
>    void setTransport(Transport t);
>    ...
>    Cache start();
> }
> {code}
> We would still want to offer a wrapper around this for Java SE users that would expose a create a CacheManager easily. This factory would want to use a CacheManagerBuilder internally to create the cache, but offer a simplified API. You would want to expose the Builder from the factory as well, offering a sensible set of defaults for SE.
> This would break backwards compatibility, as doing new EmbeddedCacheManager etc. would no longer be possible.

--
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