I'm not 100% sure I know EXACTLY what you mean by view and model. A component (Page, Panel, Border, Label, ...) has 0 or 1 markups (not necessarily a whole file) and 0 or 1 model (IModel) attached.
Page e.g. are special components. They are containers (derived from Component) and thus allow for components to be added. Again these components will have markup and a model. Usually you start with something like new MyPage() which is a container and within its constructor you add (children) additional components like labels, panels etc.. Thus after creating the page usually (but not necessarily) the whole component tree is created. Assuming a request for that page arrives at the servlet the page's render method is invoked. Render process searches for the associated markup (file or inline from parent). While reading/parsng it detects the wicket components contained. By means of its name, the corresponding component is "attached". We now have a tree of components and markup which exactly reflects that hierarchy. Another picture could be: you build up two trees, the component tree and the markup tree and boths hierarchies have to exactly match. Does that make sense? Juergen ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
