Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

Meanwhile, beta-14 includes the PageCatalog, and beta-15 (building now) improves it by dealing better with pages that have problems. On Wed, Sep 28, 2011 at 9:30 PM, Steve Eynon wrote: >> if Tapestry did all the checks at startup, before the first >> request, you would not have a good place to re

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

> if Tapestry did all the checks at startup, before the first > request, you would not have a good place to report the errors ... If you wanted to go down this line you could have a filter in place that redirected you to an error reporting page if any errors were recorded at startup. I do somethi

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

On 29.09.2011 00:25, Howard Lewis Ship wrote: 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. That would probably help. Thanks for the idea. smime.p7s Description: S/MIME Cryp

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

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 som

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

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. smim

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

Hi, I think you are looking for the part "New Component Class Validations" in the release notes . The symbol you have to use to turn off this check is SymbolConstants.UNKNOWN_COMPONENT_ID_CHECK_ENABLE

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

On 28.09.2011 01:56, Howard Lewis Ship wrote: Also, you can turn this check off, at least in 5.3 (in later releases, the option to turn off the check may be removed). See the release notes on the Tapestry home page. Sorry. I have read the release notes 2-3 times since moving from 5.2 to 5.3 a

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

Also, you can turn this check off, at least in 5.3 (in later releases, the option to turn off the check may be removed). See the release notes on the Tapestry home page. On Tue, Sep 27, 2011 at 4:55 PM, Howard Lewis Ship wrote: > See the release notes about this; it is an intentional change, to

Re: 5.3 Beta change in behaviour from Alpha with regard to event methods

See the release notes about this; it is an intentional change, to catch a common case of typos in names of event handler methods (the component id part). You may be better wrapping your components in a than a comment or . On Tue, Sep 27, 2011 at 3:49 PM, Vangel V. Ajanovski wrote: > I was using

5.3 Beta change in behaviour from Alpha with regard to event methods

I was using 5.3 alpha in production up until a couple of days, and when I changed the settings in the pom.xml to include latest beta, and rebuild, the behaviour changed and invalidated several pages in run-time. The problem is that suddenly errors occured in run-time, stating that some compone