Although I'm not using FQNs with elements other than String right now I think reducing this to String-only makes the concept of FQN significantly less powerfull. Constrains for keys in FQNs should be more or less equivalent to keys in Maps (e.g. must implement 'equals()')
I'd rather see that specific cacheloaders have the documented limitation to only support objects that return a unique value when calling 'toString()' or support some plugin-mechanism or use AOP to do the object-to-String mapping that ist required for the keys to be used by relational dBs. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848440#3848440 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848440 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
