Show me the code. Seriously, show me the listener-weak-reference code which does not fail silently when you least expect it. Which works fine in testing and then mysteriously fails in production. Show me how we can reliably catch the failure modes.
The existing listener API's may not be perfect, but at least the leaks show up pretty clearly (the Netbeans-Profiler is free and does a reasonable job). Until then, you're just wishing for ponies. I should know, I put some serious work into listener-weak-references, and I say it can't be done. But I'd be happy to be proven wrong. -- Noel. Niclas Hedhman wrote: > On Wed, Oct 28, 2009 at 5:48 PM, Christopher Brind <[email protected]> > wrote: > > > To that I oppose, on the basis that things get 'muddier' over time, > and what originally was a 'near view' component over time has a > tendency to be buried deep inside layers of 'things', and > "application's life" is not necessarily the same application anymore. >
