Hi, Method #1 - loader.get(fqn, key) - is not used in the cache loader interceptors and should be removed from the CacheLoader interface as it just adds unnecessary complexity.
I like having loader.get(fqn) to throw a NodeNotExistsException - forces implementations to be revisited rather than 'silently' failing because of changed semantics. The other option - changing the semantics of loader.get() so it returns a null only if the node doesn't exist and an empty Map if the load does but with no attribs - may result in 'silent' bugs because people haven't updated their cacheloader impl's. The downside of using an exception is the relative overhead of using an exception for a fairly common situation (trying to load a node that doesn't exist) so it isn't really an "exceptional" circumstance... Naturally such changes will be clearly documented (Javadocs, user guides and FAQs, wikis, even a blog about it). Preferences? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913738#3913738 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913738 ------------------------------------------------------- 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
