Manik and I just had a phone call, and here's the outcome (comments welcome!): - we will remove the get(node, key) method from the CacheLoader interface. It is not used and I don't think it ever will be used, because maintaining which keys have been loaded, and which not, is too complex - For the Map get(node) method, either #1 return null if node not found and an empty hashmap if no attributes are present
or #2 throw a NodeNotExists exception #1 will silently change semantics, and all CacheLoader impls have to change to conform to the new semantics #2 will force existing CacheLoader implementations to be changed I'm open for suggestions on which solution people like more. I'm slightly leaning towards #2 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913737#3913737 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913737 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
