Hi,
there's nothing wrong with yor approach, actually, it's more solid
than using (Compound)PropertyModel because you get full refactoring
support. The downside is of course code verbosity. Unless java get
property expression there's not much we can do about it though :-/
-Matej
On 8/24/07, Sam Hough <[EMAIL PROTECTED]> wrote:
>
> Does anybody use any other data binding than the built in Wicket classes?
>
> We have few complex objects rather than lots of objects with lots of fields
> so having the binding more explicit e.g.:
> add(new TextField("value", new ModelString() {
> public void setString(String p) {
> model.setValue(p);
> }
> public String getString() {
> return model.getValue();
> }
> }));
> Is tempting as we would get more tool support in eclipse etc and it is more
> obvious what is going on. Obviously the huge downside is that it is much
> more verbose than:
> add(new TextField("value"));
>
> Sorry I'm being so greedy on this forum. Still not switched my thinking from
> the two extremes of struts and GWT.
>
>
> --
> View this message in context:
> http://www.nabble.com/Alternative-to-Wicket-data-binding-tf4322899.html#a12310156
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
