Hello, On Tue, 26 Feb 2008, Sebastiaan van Erk wrote: > Then a refactor of the customerName property (and the getCustomerName() > method) in an IDE such as Eclipse or NetBeans will *silently* break the > above code, which you will discover only at runtime... > > The proxy based approach solves exactly this problem.
We have found extensive developer tests (produced with TDD / BDD) to be a very effective solution to this problem. I prefer the current, terser syntax because of better readability, even though the string literals breaking in refactorings bother me too. It's a pity that Java in its current state seems to force one to produce a lot of clutter in the proxy-based approach, which is otherwise a very neat idea. For a Wicket UI, it's fairly easy to get 100 % branch coverage. And behavior-driving your code is more effective than "just writing it" anyway (produces better code faster), so it's a double win :) Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
