[jboss-dev-forums] [Design of JBossCache] - Re: Classloader leak via CacheImpl.invocationContextContaine
manik.surtani@jboss.com
do-not-reply at jboss.com
Fri Jun 15 12:28:39 EDT 2007
I like the varargs approach, except that it uses varargs to make a param optional (1 instance or none) rather than several instances, which is what varargs were desigend for (and hence IDEs representing them as such). A *bit* hacky, IMO.
The other approach is to allow people to pass in many Options, like Jason mentioned, such as node.get(key, Option.FORCE_WRITE_LOCK, Option.FAIL_SILENTLY) but this means we'd need to aggregate the options passed in into a single one - not hard to do, just annoying and defeats the purpose of an Option class.
Thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054831#4054831
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054831
More information about the jboss-dev-forums
mailing list