[infinispan-dev] [ISPN-153] Binding Cache/CacheManager to JNDI

Galder Zamarreno galder at redhat.com
Mon Oct 19 04:07:37 EDT 2009


https://jira.jboss.org/jira/browse/ISPN-230

I've keep the scope of https://jira.jboss.org/jira/browse/ISPN-153 as it 
is, simply limit it to testing it.

On 10/17/2009 04:51 PM, Manik Surtani wrote:
> Perhaps create a separate JIRA to add this feature to Infinispan then,
> as a low-prio thing for 4.1.0 or 5.0.0, maybe someone will contrib it
> at some stage.
>
> On 16 Oct 2009, at 16:06, Brian Stansberry wrote:
>
>> The AS already handles this with minimal effort for its impl of the
>> JBC
>> CacheManager. So don't do it to make my life easier. If anything gets
>> bound in JNDI inside AS for the standard clustering services, I want
>> the
>> AS to be what controls that, and I don't want to have to work with any
>> Infinispan configuration or integration API to achieve it.
>>
>> On 10/16/2009 06:42 AM, Manik Surtani wrote:
>>> Hmm, I'm not sure about this - this adds bloat to Infinispan, and we
>>> shouldn't really care about how people share instances.  However, it
>>> would make peoples' lives easier and increase adoption.  What do
>>> others think?
>>>
>>>
>>> On 16 Oct 2009, at 12:29, Galder Zamarreno wrote:
>>>
>>>> Hi,
>>>>
>>>> Re: https://jira.jboss.org/jira/browse/ISPN-153
>>>>
>>>> Apart from testing itself, does it make sense to include the ability
>>>> of
>>>> binding to JNDI, using
>>>> org.jboss.util.naming.NonSerializableFactory to
>>>> to bind a non-serializable object into a local JNDI context, within
>>>> Infinispan itself?
>>>>
>>>> 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 should, in theory, ease JNDI binding in AS and other apps
>>>> servers
>>>> without the need of extra code in those environments.
>>>>
>>>> Thoughts? Brian, would you find this useful?
>>>>
>>>> Cheers,
>>>> --
>>>> Galder Zamarreño
>>>> Sr. Software Engineer
>>>> Infinispan, JBoss Cache
>>>> _______________________________________________
>>>> infinispan-dev mailing list
>>>> infinispan-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>>
>>> --
>>> Manik Surtani
>>> manik at jboss.org
>>> Lead, Infinispan
>>> Lead, JBoss Cache
>>> http://www.infinispan.org
>>> http://www.jbosscache.org
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>>
>> --
>> Brian Stansberry
>> Lead, AS Clustering
>> JBoss by Red Hat
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

-- 
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache



More information about the infinispan-dev mailing list