On 08/04/2009 06:40 PM, Brian Stansberry wrote:
> Galder Zamarreno wrote:
>>
>>
>> On 08/04/2009 06:23 PM, Brian Stansberry wrote:
>>>
>>> Also, unless there's a really good reason not too, let's try to keep
>>> things logically the same between the Infinispan and JBC integrations.
>>> Makes m
Galder Zamarreno wrote:
>
>
> On 08/04/2009 06:40 PM, Brian Stansberry wrote:
>> Galder Zamarreno wrote:
>>>
>>>
>>> On 08/04/2009 06:23 PM, Brian Stansberry wrote:
>
>
>
Also, unless there's a really good reason not too, let's try to keep
things logically the same between the I
On 08/05/2009 04:04 PM, Brian Stansberry wrote:
> Galder Zamarreno wrote:
>>
>>
>
> Sounds like this has diverged quite a bit from the JBC integration then.
> In your initial message you were discussing names:
>
> hibernate.cache.region.ispn4.cfg.entity
> hibernate.cache.region.ispn4.cfg.collect
Galder Zamarreno wrote:
>
>
> On 08/05/2009 04:04 PM, Brian Stansberry wrote:
>> Galder Zamarreno wrote:
>>>
>
>>>
>>
>> Sounds like this has diverged quite a bit from the JBC integration then.
>> In your initial message you were discussing names:
>>
>> hibernate.cache.region.ispn4.cfg.entity
>>
On 08/05/2009 12:52 PM, Brian Stansberry wrote:
> Semi-tangent: in general I really dislike if people have to configure
> JBC/Infinispan to get standard behaviors (e.g. eviction). Much better if
> people can use the standard configuration mechanism of whatever service
> is using JBC/Infinispan, an
