A couple more: Tapestry shares any single page instance between all threads -> should be "shares every single page".
Storing only few values of persistent fields the session instead of entire page's structure -> The most part of Tapestry framework get along well without using HttpSession Tapestry also provides you with features that allow you to avoid using session -> using sessions? Tapestry will search or a template file with the same name writer.end() written twice Finally, we will see how to prevent the rendering of a page, if its state couldn't restored properly, and send an alternative response This is why why the annotation, unlike @ActivationRequestParameter You may assign values to fields of a page without to care about thread-safety This means that values of page' mutable fields are lost unless the field is a persistent property. As you can see, the page looks still same Tapestry monitors the changes to a persistent property and stores the value into a storage as soon as it is modified concentrate on you business logic without to bother about the details Fortunately Tapestry takes over the most of the steps These data can be read by accessing the properties of the User instance The name attribute of field tells which group The Select component has to required parameters In the modern world almost all data are related to dates This data are written to local temporary file The most of the components covered in this section I'll show you some more advanced component variable number of fields without to pollute your templates with if-else constructs other object that is capable to do that Finally, the report data are streamed to the client So will explore the AjaxFormLoop Will we use this component inside a form in order to add or remove from fields dynamically. 2 errors Consider you want to create plugin for Tlog This is what the TriggerFragment mixin is applied to the shipToAnotherAddress checkbox components they are applied on with new functionality The method takes a ISO 4217 currency code and returns a Calendar(Currency instance) instance for given code Currently Tapestry provides following built-in encoders, which cover a plenty of use Tapestry provide a set of built-in validators A validator is associated with a type it is able to validate instances of Needles to say, duplicating code should be avoided as far as possible For most validator this method returns false. In order to be more useful, the component take a name to be greeted In listing 9.8 the component's parameter is named css, even though the( parameter is named class, not css) The may be void, return null or a boolean value Based on that convention Tapestry will recognized the method Based on that convention Tapestry will recognized the method Note that the second argument is an varargs whose Thanks, Bogdan. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-book-some-minor-typos-in-Chapter-2-tp5715402p5715821.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
