-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Facade & DTO Pattern
PostPosted: Thu Apr 16, 2009 3:00 pm 
Newbie

Joined: Thu Apr 16, 2009 1:53 pm
Posts: 2
Hi Emmanuel,

I don't read the spec yet, but I would like to know if you took into account the facade + dto pattern while writing the specs.

The DTOs are often slightly different of the underlying model and especially when you implement this pattern for remoting purpose like WS.

So, following the DRY principle I would reuse the constraints and validators in this layer. In this specific case what is the best approach? Should I reuse property constraints in new DTO validators?

Your input will be appreciated,

Regards,
Alexandre Garino


Top
 Profile  
 
 Post subject: Re: Facade & DTO Pattern
PostPosted: Mon Jun 22, 2009 1:38 pm 
Hibernate Team
Hibernate Team

Joined: Sun Sep 14, 2003 3:54 am
Posts: 7256
Location: Paris, France
DTO and DRY are somewhat antagonists. Not sure how to reconcile them. But theoretically, a framework could somehow decide to "transfer" constraints from one property to an other. This would need some layer of metadata from this particular framework but BV exposes enough data via the metadata API I think.

_________________
Emmanuel


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.