too much caffine for me yesterday (very bad for me resulting in mental overdrive and then no sleep). even though i'm tired now, it the manic phase may have produced a positive side effect - or possibly just another mad idea...
a lot of difficulties (including issues with hot deployment) arise from JCL caching classloaders. most of these issues should be addressed by using a weakhashtable but there are certain cases where even a weak hash table cannot solve the issue. the reason for indexing on classloaders is to allow configurations to be saved on a per classloader basis. it strikes me that identity should be as good as equality for this indexing. if so, then we could use System.identityHashCode as the index rather than the actual classloader. please feel free to spot the flaws with this plan :) - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
