On Tue, Feb 5, 2013 at 10:05 AM, Marios Skounakis <[email protected]> wrote: > Understood. I am still unclear why wicket would behave differently in > deployment and development configuration with respect to missing components > in the markup. Is there any actual use case for this? If not, I believe it > would be better to have a consistent behavior.
The check costs CPU time. The check is there for developers to detect missing stuff/errors. We detect them during the DEVELOPMENT phase. As long as Wicket is able to function correctly and render pages without problems, there is IMO no problem with letting your users be able to use the application in production. There is a reason why we ship Wicket out of the box with DEVELOPMENT mode enabled: because developers are our primary audience. As a developer it is your responsibility to use the framework as intended. This working is actually well documented in Wicket in Action and the various talks I gave around the world. > Of course, changing the way deployment configuration behaves currently > could break working apps who are now functional because an exception is not > being thrown... And that would be a bad thing, since some developers actually depend on this to work like this (don't ask me why though). Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
