Francisco Diaz Trepat - gmail wrote:
>
> What would be the purpose of a class with only getters and setters besides
> adding a new layer to the software?
>
Well (in the absence of further information), there would be no purpose.
But there's no need to have these extra objects in the first place. If your
services are written in Java, just use the pojo BOs (or DTOs) returned by
these services as your model. If your services are written in some other
language (C++) and return xml-serialised versions of BOs/DTOs, then just use
the xml as the model (as Igor explained). No need for another set of
objects, at least not for Wicket models.
Or am I still missing something?
--
View this message in context:
http://www.nabble.com/How-to-best-deffend-models-and-entity-classes-tf3960566.html#a11288105
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
