1. In general, TreeCacheAop only has advantage is your pojo has long life time. So most of the time I think issuing removeObject explicitly is not a problem. But yeah, I agree that it is still an issue. I just didn't have good solution. But there is a plan to refactor it in 2.0 due in 4-5 months.
2. This is also in the todo list using annotation. I am shooting for 1.4. One other option is you can mark it transient (althgouhg it is sort of ad hoc). 3. Yes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931473#3931473 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3931473 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
