:07 AM
To: [EMAIL PROTECTED]
Subject: [Hibernate] Business Rules
Hi all,
Please, take a look at the the following scenario:
A "Order" persistence class is associate to a "Customer" persistence class
and the business rules is:
We can not make a new Order if the Customer associ
On 28 Oct (10:33), Miguel Henley wrote:
> 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 ?
No, this
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 tha
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 d
restrictions may change!
Eric
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf
> Of Miguel
> Henley
> Sent: Tuesday, October 28, 2003 1:07 PM
> To: [EMAIL PROTECTED]
> Subject: [Hibernate] Business Rules
>
>
>
> Hi all,
Hi all,
Please, take a look at the the following scenario:
A "Order" persistence class is associate to a "Customer" persistence class and the
business rules is:
We can not make a new Order if the Customer associated with that Order has some credit
restrictions.
Where is the right place to put
