_MarkupContainer implements a full set of methods to manage children components. The basic operations we can do on them are: • add one or more children components (with method add). • remove a specific although not all of them implement a detaching policy (like the Model class). Usually detaching operations are strictly dependent on the persistence technology adopted for model objects (like a relational datetime.PatternDateConvert and must use the previously retrieved date format to perform conversion operations. Now to tell our component to use this converter we must return it overriding FormComponent's

3). MarkupContainer implements a full set of methods to manage children components. The basic operations we can do on them are: • add one or more children components (with method add). • remove a specific although not all of them implement a detaching policy (like the Model class). Usually detaching operations are strictly dependent on the persistence technology adopted for model objects (like a relational possible operations that can be performed on the object. In the case of a Wicket application the available operations are clearMarkupCache and clearLocalizerCache: 203 With these two operations we can

“Transparent” AJAX Wicket simplifes AJAX development controlling via Java the following basic operations: ● Generate a page unique id for the DOM element of a component. ● Write a callback for an event of a component. ● Execute JavaScript code as response to a specifc event. For the frst three operations we won’t write a single line of JavaScript! Handle AJAX events ● Now we can “ajaxify” components

3). MarkupContainer implements a full set of methods to manage children components. The basic operations we can do on them are: • add one or more children components (with method add). • remove a specific although not all of them implement a detaching policy (like the Model class). Usually detaching operations are strictly dependent on the persistence technology adopted for model objects (like a relational possible operations that can be performed on the object. In the case of a Wicket application the available operations are clearMarkupCache and clearLocalizerCache: 194 With these two operations we can

3). MarkupContainer implements a full set of methods to manage children components. The basic operations we can do on them are: • add one or more children components (with method add). • remove a specific although not all of them implement a detaching policy (like the Model class). Usually detaching operations are strictly dependent on the persistence technology adopted for model objects (like a relational possible operations that can be performed on the object. In the case of a Wicket application the available operations are clearMarkupCache and clearLocalizerCache: 193 With these two operations we can