On Jan 19, 2011, at 4:23 PM, Mircea Markus wrote:
On 19 Jan 2011, at 15:11, Galder Zamarreño wrote:
>
> On Jan 19, 2011, at 10:31 AM, Galder Zamarreño wrote:
>
>> On Jan 18, 2011, at 6:51 PM, Manik Surtani wrote:
>>
>>> On 18 Jan 2011, at 16:17, Pete Muir wrote:
>>>>
>>>> 12)
http://community.jboss.org/wiki/InfinispanInteractiveTutorialwithScala
>>>>
>>>> For "Cache with Transaction Management" I was not seeing TX
semantics being obeyed, I saw the size increment as a added key-value pairs
which cache operation?
I imagine the size only increments within the transaction context? i.e. if you suspend
the uncommitted transaction and run the same operation again, you don't see
transaction's modifications.
Right, so you're saying that a transaction should see its own changes even if
they're uncommitted, correct? If so yeah, it should work as is and wiki needs
modifying.
>>>
>>> Galder, this as well?
>>
>> I'll check it out.
>
> I created
https://issues.jboss.org/browse/ISPN-882 - This behaviour is like this
since since we accepted (Mircea?) the following community bug report:
https://issues.jboss.org/browse/ISPN-679
>
> Can we get an agreement on this? I think it should work as it did originally.
You mean cache.values()? should not be tx aware? I think it should be consistent with all
the other ops, like put, get etc. (which are tx aware).
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache