One thing that came to mind was to add a general configuration set that would allow Node key values to be mapped into specific table columns. (Sort of a poor man's JPA.) Data would be therefore stored in a way that was easily accessible and managed by your DBA. But really the only practical use I considered would be for managing timestamps of data. But instead of writing code, one thing you could consider is simply adding a update timestamp column to the cache loader's table, which is populated through a trigger. Then a background process run by your DBA could cull the data as necessary. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223792#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...