So if you do:
cacheA.putObject("/test", pojoA); // pojo attached on cache A
pojoA1 = cacheB.getObject("/test");
pojoA1 is null? You've definitely got something weird going on then. That's
just basic stuff. Not sure what to say about that :( Hopefully Ben will have
some idea.
Well, let's just pretend that issue is solved. :-) Re: the JBCACHE-674 problem
Ben mentioned with calling:
cacheA.putObject("/test", pojoA);
cacheB.putObject("/test", pojoB);
A workaround should be to just do this:
cacheA.getObject("/test");
cacheA.putObject("/test", pojoA);
cacheB.getObject("/test");
cacheB.putObject("/test", pojoB);
If you call getObject() on the 2nd cache before replacing the object, that's
enough to put the cache into a state where it detects that an object
replacement has happened. (Of course you call getObject() on both caches,
because you don't know which one will be the "2nd" cache).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954197#3954197
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954197
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
