those are resulting in much less code. And it is still very readable. Ok refactor is a problem then
Isn't it a pitty then you can do this:
PropertyModel(User.getName, user)
and no the () after getName are not forgotten :))
johan
On 11/16/05, Janne Hietamäki <[EMAIL PROTECTED]> wrote:
Johan Compagner wrote:
> why do you think property models really suck?
> Because of that string that is not type save ofcourse (so refactor
> won't notice it)
> I get those drawbacks do you have others?
>
Yep, refactoring is the problem. I want to keep my code clean and
logical, and for that I need to be able to refactor my models however I
want. I don't like scripting on markup, so I like wicket. But even less
I like any kind of scripting on my code.
--
Janne Hietamäki
Cemron Ltd
http://www.cemron.com/
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&opclick
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
