[infinispan-issues] [JBoss JIRA] Updated: (ISPN-230) Enable JNDI binding of Cache/CacheManager out of the box

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño updated ISPN-230:
----------------------------------

      Fix Version/s: 6.0.0.FINAL
                         (was: 5.1.0.BETA1)
                         (was: 5.1.0.FINAL)
    Forum Reference: http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001660.html  (was: http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001660.html)


AS does not need this from us and there's very good workaround for anyone that wants to hook Infinispan into JNDI as shown in:
https://docs.jboss.org/author/pages/viewpage.action?pageId=5832910 

> Enable JNDI binding of Cache/CacheManager out of the box
> --------------------------------------------------------
>
>                 Key: ISPN-230
>                 URL: https://issues.jboss.org/browse/ISPN-230
>             Project: Infinispan
>          Issue Type: Feature Request
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>            Priority: Minor
>              Labels: hackathon
>             Fix For: 6.0.0.FINAL
>
>
> Note that implementing this has no urgency since it does not really help Brian S for the JBoss AS integration.
> See: http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001663.html
> So, I'm thinking that we could have a <jndi name="xyz"/> configuration 
> option both at the global level (for Cache Manager) and at the Cache 
> level. So,
> - if <jndi/> was present in the global section, we'd bind CacheManager 
> to java:CacheManager
> - if <jndi name="xyz"/> was present in the global section, we'd bind 
> CacheManager to java:xyz
> - if <jndi/> was present in the cache section, we'd bind Cache to 
> java:<name-of-the-cache>
> - if <jndi name="xyz"/> was present in the cache section, we'd bind 
> Cache to java:xyz

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira