[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1057) Modifying a detached POJO still shows changes in the cache (under /__JBossInternal__) and replicates it to other caches

Galder Zamarreno (JIRA) jira-events at lists.jboss.org
Wed May 16 07:28:56 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBCACHE-1057?page=comments#action_12362338 ] 
            
Galder Zamarreno commented on JBCACHE-1057:
-------------------------------------------

Jason and I saw this happening with Collections, but it does actually happen 
with normal attributes as well.

I have just run the renovated PojoCache tutorial and it fails with normal fields.

I should be committing the tutorial today.

> Modifying a detached POJO still shows changes in the cache (under /__JBossInternal__) and replicates it to other caches
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1057
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1057
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: PojoCache
>    Affects Versions: 2.0.0.CR1
>            Reporter: Galder Zamarreno
>         Assigned To: Jason T. Greene
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> Two PojoCache instances replicated. Add a POJO in the first instance and then detach() it from the second 
> cache instance. This removes the POJO from the cache. But if you now call a setX() on the POJO from 
> the first instance, first, the cache stores the new value under /__JBossInternal__ and it also replicates it to 
> the second cache instance. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list