_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 FileSystems can be implemented as described here: http://docs.oracle.com/javase/7/docs/technotes/guides/io/fsp/filesystemprovider.html 16.16. Resourcen derived through models Another way to receive external

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 FileSystems can be implemented as described here: http://docs.oracle.com/javase/7/docs/technotes/guides/io/fsp/filesystemprovider.html 16.17. Resources derived through models Another way to receive external

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 FileSystems can be implemented as described here: http://docs.oracle.com/javase/7/docs/technotes/guides/io/fsp/filesystemprovider.html 16.17. Resources derived through models Another way to receive external

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 FileSystems can be implemented as described here: http://docs.oracle.com/javase/7/docs/technotes/guides/io/fsp/filesystemprovider.html 16.17. Resources derived through models Another way to receive external

“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