Killed long argument Summary: * disable it in development profile, but turn it on in quickstart#init with comment * provide link to switch it on on exception page * add debug profile * switch markup location to 'on' in development mode * add Java based profiles, with non-deprecated web.xml init parameters [1] * add Wicket development mode dashboard to development mode visible on all pages * add deployment profile to quickstart pom that switches web.xml to deployment mode
[1] the web.xml settings provide a great opportunity to create a war based on profiles using filtering with Maven and Ant. Martijn On 7/6/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
the new error reporting feature, that one that throws two exceptions per component, is really making development not enjoyable. it slows down request processing significantly and might give noobs the wrong impression. it is valuable information for noobs, but imho after using wicket for a week you will probably encounter such problems rarely. [ ] disable this feature by default, put instructions on how to enable it into component-not-found related exception messages [ ] leave it enabled by default -igor
-- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
