Hello, I'm thinking about how to access rarely changed data the right way.
An example: I store categories in the database; they may change once a week. So normally I would store them in Application Scope, but as I triggered out, there is no easy way to invalidate the Application scope - in case of a change (only if I call a method to reinitialize (@create) the Component). Now my second thought was about using Hibernate cache to store the categories in Memory. But I don?t really know how to handle the update. Is there a design pattern for this problem and what is the better approach (Application Scope or cache)? Important is, that the categories are not reloaded every request but that they are updated if they were changed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928638#3928638 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928638 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
