or create models that bind to xml, something like
class XmlPropertyModel(String xml, String path) extends
AbstractReadOnlyModel {
Object getObject() { return XmlUtils.getPath(xml, path); }
}
add(new TextField("foo", new XmlPropertyModel(xml, "address.street"));
also create anl XmlCompoundPropertyModel(String xml) and you can do add(new
TextField("address.street"));
wicket can bind to anything, not just pojos.
-igor
On 6/22/07, severian <[EMAIL PROTECTED]> wrote:
I'm not sure I fully understand your situation, but if your wicket front
end
is obtaining xml-serialised versions of business objects (or data transfer
objects or whatever), can you not generate a simple Java version from the
xml schema? Then perhaps your colleagues objections about having to
"redo"
the objects will disappear...
--
View this message in context:
http://www.nabble.com/How-to-best-deffend-models-and-entity-classes-tf3960566.html#a11247700
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
