On Thu, 29 Nov 2007, Gervais wrote:
> DTO is a design that can be not only in J2EE.
>
> I like the idea that Wicket can manipulate directly domain objects but
> not to give many objects to wicket page's.
When doing real remoting DTOs might make sense. With Wicket
pages I don't quite see how would that happen. We typically
have components looking up the data they need themselves,
using injected services. But obviously you might be in a
different situation.
> I like that
> public class APage extends WebPage {
> public APage(ADomainBean bean) {.. }
>
> But not
> public class APage extends WebPage {
> public APage(ADomainBean bean0, ANotherDomainBean bean1,
> YetAnotherDimainBean bean2, .. ) {.. }
To me it seems as if that would just be hiding a design
problem of APage having too much responsibility (and thus
not following the single responsibility principle).
Anyway, this is getting off-topic, so maybe we'll have to
keep it down or get a room :)
> student project, i must change the presentation layer for another web
> presentation framework or Swing with remoting)
For remote client-server some DTOs might make sense, but as
with any optimisation you shouldn't do it too early.
Best wishes,
Timo
--
Timo Rantalaiho
Reaktor Innovations Oy <URL: http://www.ri.fi/ >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
