. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 14.3. When are components dequeued? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 16.8. Put JavaScript inside page body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve it release after release. However Wicket never provided a freely available documentation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 14.3. When are components dequeued? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 16.8. Put JavaScript inside page body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve it release after release. However Wicket never provided a freely available documentation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 14.3. When are components dequeued? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 16.8. Put JavaScript inside page body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve it release after release. However Wicket never provided a freely available documentation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 14.3. When are components dequeued? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 16.8. Put JavaScript inside page body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve it release after release. However Wicket never provided a freely available documentation

input controls, links, etc...), are pure class instances. Since pages are class instances they live inside the JVM heap and we can handle them as we do with any other Java class. ● This approach is very oriented frameworks bring to web development the same kind of abstraction that GUI frameworks ofer when we build a desktop application. ● This kind of framework hides the details of the HTTP protocol application is a standard Java EE web application, hence it is deployed through a web.xml fle placed inside folder WEB-INF: