Shortly after we discovered this issue we made the same modification to our application. While not absolutely fool proof (and what is anyway?) it does shorten the loop on discovering these issues. However, I have actually seen this create its own problems when developing with a heavy use of panels and custom components. A lot of times it is useful to see where those wicket: tags are in the fully rendered document so you can figure out what parts of the html belong where so as to allow your css ninja to create the correct layout for you because the designers don't think in terms of the same kind of components us wicket developers do.
In any case your suggestion is an excellent one and I recommend it to anyone developing anything but the most trivial of applications. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Works-in-Development-Mode-but-not-in-Production-Mode-tp2300335p2302610.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
