. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 28.4. Write own measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . direct children) and streamChildren (which contains all children). Both Panel and WebPage have their own associated markup file which is used to render the corresponding component. If such file is not provided markup.html.panel. Just like its parent component WebMarkupContainer, 29 Fragment doesn’t have its own markup file but it uses a markup fragment defined in the markup file of its parent container, which

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 27.4. Write own measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iterator or using visitor pattern1 with methods visitChildren. Both Panel and WebPage have their own associated markup file which is used to render the corresponding component. If such file is not provided wicket.markup.html.panel. Just like its parent component WebMarkupContainer, Fragment doesn’t have its own markup file but it uses a markup fragment defined in the markup file of its parent container, which

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 28.4. Write own measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . direct children) and streamChildren (which contains all children). Both Panel and WebPage have their own associated markup file which is used to render the corresponding component. If such file is not provided markup.html.panel. Just like its parent component WebMarkupContainer, 30 Fragment doesn’t have its own markup file but it uses a markup fragment defined in the markup file of its parent container, which

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 28.4. Write own measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . direct children) and streamChildren (which contains all children). Both Panel and WebPage have their own associated markup file which is used to render the corresponding component. If such file is not provided markup.html.panel. Just like its parent component WebMarkupContainer, 29 Fragment doesn’t have its own markup file but it uses a markup fragment defined in the markup file of its parent container, which

is org.apache.wicket.MarkupContainer: Wicket pages and panels ● Both Panel and WebPage have their own associated markup fle which is used to render the corresponding component. When a panel is attached