>
> Nope. Typical reasons to use PropertyModels explicitly is when you
> don't use a CompoundPropertyModel on the parent, or when you want to
> use IDs that are different from the property expressions you want the
> model to work on. Also, note that you can use completely different
> models as well; property models are convenient but not the only
> options (as you can read in the WIKI).
CompoundPropertyModel cpm = new CompoundPropertyModel (xxx);
Form f = new Form("form",cpm);
f.add(new TextField("username"));
f.add(new TextField("notinmodel", cpm.bind("address"));
