Nick Heudecker wrote:
The right answer is to have automated unit tests to test your
refactoring.
Not that I do that 100% either. :)
Unit tests are not really any answer to this, of course I have the unit
tests, but it's still a pain in the ass when I have some 50 classes
needing refactoring when doing a single modification on a model. I don't
want to do that when I have a computer for doing such jobs.
I'll have to think my original idea, it would reduce quite lot of code
compared to the IModel.
Label l = new Label(id , new QueryModel(user){ String run(User user){
return user.getGroup().getName(); }});
Would really be enough to do get/setObject.. This would be a kind of
compromise between refactoring and amount of the 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&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
