You can duplicate the same class hierarchy in the ui.
public class TaskFormPanel<T extends Task> extends Panel {
public TaskFormPanel(String id, IModel<T> model)
super(id, new CompoundPropertyModel(model));
add(new TextField("d"));
add(new TextField("e));
add(new Button("submit) {
(...)
}
}
}
public class Task1FormPanel extends TaskFormPanel<Task1> {
public TaskFormPanel(String id, IModel<Task1> model)
super(id, model);
add(new TextField("a"));
add(new TextField("b));
add(new TextField("c"));
}
}
public class Task2FormPanel extends TaskFormPanel<Task2> {
public TaskFormPanel(String id, IModel<Task1> model)
super(id, model);
add(new TextField("x"));
add(new TextField("y));
add(new TextField("z"));
}
}
And the HTML files:
TaskFormPanel:
<wicket:panel>
<wicket:child/>
<label>d</label> <input wicket:id="d">
<label>e</label> <input wicket:id="e">
<input type="submit" wicket:id="submit"/>
</wicket:panel>
Task1Panel.html:
<wicket:extend>
<label>a</label> <input wicket:id="a">
<label>b</label> <input wicket:id="b">
<label>c</label> <input wicket:id="c">
</wicket:extend>
Task2Panel.html:
<wicket:extend>
<label>x</label> <input wicket:id="x">
<label>y</label> <input wicket:id="y">
<label>z</label> <input wicket:id="z">
</wicket:extend>
Note: make sure you use some loadabledetachablemodel to wrap the task objects in if they contain a reference to a thread otherwise you will run into serialization issues. A singleton registry that stores your tasks and can return them by some random key is enough.