The main problem is not the time it took to fix, but the fact that i
accidentally stumbled on a page not working anymore because a coworker
had changed the java code from new SimpleAttributeModifier("onClick",
...) to "onclick" innocently expecting his change would not have any
effect. You don't want accidents like this to go to a production
environment without at least wicket screaming bloody murder, but then
you still have to notice the warning, an fix it. It would be much
simpler if wicket fixed it automagically for you.Maurice On 5/31/07, Timo Rantalaiho <[EMAIL PROTECTED]> wrote:
On Wed, 30 May 2007, Johan Compagner wrote: > here we have a case that the design says one thing and the java code another > so its a mismatch > what should happen then? > Today maurice had such a case and that did cost him quite some time to track > down. > Maybe in development mode we test for it somehow and then throw an > exception? Or just throw an exception always -- is there any case in which you would want to have a differing case in markup than in code? - Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ >
