So, do you think that for each persitence class it's a good design decision to create a Manager class ? The Manager class first check the business rules and if it's Ok calls the save / update / delete methods of the session. Is it right ?
Miguel. -----Mensagem original----- De: Christian Bauer [mailto:[EMAIL PROTECTED] Enviada em: Terça-feira, 28 de Outubro de 2003 09:10 Para: [EMAIL PROTECTED] Assunto: Re: [Hibernate] Business Rules On 28 Oct (12:38), Eric Pugh wrote: > I lean towards not putting that kind of logic in some sort of Manager > object.. I find that when you start mixing busienss logic with data > objects, soon your business logic tier and data tier become all intertwined. Interestingly, thats the reason for a domain model in the first place. :) -- Christian Bauer [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
