variable. And this is just half of the work we have to do as we must implement the inverse path (load data from Java to the web form). Moreover, most times our forms will use a JavaBean or a POJO as providing its constructor with the corresponding page id: //load page version with page id = 3 PageReference pageReference = new PageReference(3); //load the related page instance Page page = pageReference.getPage(); like we did in the previous example, obtaining something like this: Person person = new Person(); //load person's data... Label label = new Label("name", new Model(person.getName())); However this solution

variable. And this is just half of the work we have to do as we must implement the inverse path (load data from Java to the web form).Moreover, most of the times our forms will use a JavaBean or a POJO providing its constructor with the corresponding page id: //load page version with page id = 3 PageReference pageReference = new PageReference(3); //load the related page instance Page page = pageReference.getPage(); like we did in the previous example, obtaining something like this: Person person = new Person(); //load person's data... Label label = new Label("name", new Model(person.getName())); However this solution

variable. And this is just half of the work we have to do as we must implement the inverse path (load data from Java to the web form). Moreover, most times our forms will use a JavaBean or a POJO as providing its constructor with the corresponding page id: //load page version with page id = 3 PageReference pageReference = new PageReference(3); //load the related page instance Page page = pageReference.getPage(); like we did in the previous example, obtaining something like this: Person person = new Person(); //load person's data... Label label = new Label("name", new Model(person.getName())); However this solution

variable. And this is just half of the work we have to do as we must implement the inverse path (load data from Java to the web form). Moreover, most times our forms will use a JavaBean or a POJO as providing its constructor with the corresponding page id: //load page version with page id = 3 PageReference pageReference = new PageReference(3); //load the related page instance Page page = pageReference.getPage(); like we did in the previous example, obtaining something like this: Person person = new Person(); //load person's data... Label label = new Label("name", new Model(person.getName())); However this solution

static resources is a very common task. With Wicket we can specify not just the static resource to load, but also its dependencies and its loading priority. Static resources ● In general static resources