Part of Tapestry's philosophy is lazy loading of pages and components on an as-needed basis. This has good points and bad points ... good points are very fast startup which I find very important. The bad side is that a lot of checks occur when the page is lazily loaded (when first needed), and some things people want (such as a @Path annotation on pages to control the URL for that page) aren't possible.
Further, if Tapestry did all the checks at startup, before the first request, you would not have a good place to report the errors ... errors logged to the console are not nearly as nice as the full exception report page. A thought: a built in page that, when it renders, identifies and loads all pages in the application, which should flesh out most of the errors in most pages. So the "PageCatalog" page would either generate a list of all pages, or an exception report for the first error loading a page. Quite doable. On Wed, Sep 28, 2011 at 1:01 PM, Vangel V. Ajanovski <a...@ii.edu.mk> wrote: > On 28.09.2011 10:32, Dragan Sahpaski wrote: >> >> The symbol you have to use to turn off this check is >> SymbolConstants.UNKNOWN_COMPONENT_ID_CHECK_ENABLED. >> > Actually, I like this check, but it would be better if it was possible to > happen at application startup, not on first access to the page. > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
