michael,
Sorry that it wasn' clear before but I probably know where is the problem. You
are doing:
| cacheA.putObject("/test", pojoA); // pojo attached on cache A
|
| cacheB.putObject("/test", pojoB); // pojo attached on cache B as well
|
| pojoA.setBlah(xx); // will have problem here
|
Any reason doing simultaneous pojo putObject from both nodes? This is a problem
that currently PojoCache don't handle. I have opened a Jira (JBCACHE-674) to
track this.
Alternative is to use different fqns for different POJOs. Remember that POJO
lifetime is not supposed to be short-lived, otherwise, PojoCache won't be
effective.
Just to confirm, the regular usage:
| cacheA.putObject("/test", pojoA); // pojo attached on cache A
|
| pojoA1 = cacheB.getObject("/test");
|
| pojoA.setBlah(xx); // will have problem here
| print(pojoA1); will get updated.
|
will work, correct?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953869#3953869
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953869
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
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
