Hi guys, I think I'm about to get into an argument about models and I wish
to discuss it here first, if you don't mind.
Here is the general argument.
Entity classes with only getters and setters don't do any good because they
just put an innecesary extra layer in the software:
public class Person{
String firstName;
String lastName;
public Person(){
}
public String getFirstName(){
return firstName;
}
public void setFirstName(String firstName){
this.firstName=firstName;
}
etc...etc..
}
I preatty much disaggree with this, and cannot find the right explanation.
As for wicket, we are bound to used wicket models with some kind of entity
holder (as Person is).
For instance one request I just got is:
As the C++ libraries with business logic will return XML representing
objects (like *Municipality, Person, Tax, etc.*) on the other side of the
business server lets not redo those objects in the wicket project. For
example generating something like:
private final Tax taxEntity = new Tax(); //Being Tax something like
Person Above.
Form form = new Form("incomeTaxForm", new CompoundPropertyModel(
this.taxEntity));
Or worst, for this opinion against models, a model bound specifically for
one form. Business logic applyed here is, we will need to code a bit more.
If you can, please help me construct a more reasonable explanation than
"ehhmmmm dadaaaaa!!!" :-) [EMAIL PROTECTED]
best regards,
f(t)
-------------------------------------------------------------------------
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
