RE: [Hibernate] Business Rules

2003-10-28 Thread Urberg, John
I see the following two options: 1) Make the constructor on Order private and use a static factory method on Order to first verify the Customer does not have credit restrictions before creating the Order. 2) Make the constructor on Order package level access and add a method to Customer to create

Re: [Hibernate] Business Rules

2003-10-28 Thread Christian Bauer
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

RE: [Hibernate] Business Rules

2003-10-28 Thread Eric Pugh
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. I would lean towards OrderManager or something where you have a call like: OrderM