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 Baue
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
Hello,
I know that I can implement the Validatable interface at the persistence class to
check for invariant.
But supose that the invariant depends of the operation -- if the persistence class is
going to be "inserted" at the database the rules is not the same for the update
operation.
What is
Hi,
It's not clear to me the difference between the XML element and the XML
element at the hibernate mappings file.
Can someone explain me that ?
Regards,
Miguel.
---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you
Hello All,
I am new in this list and I have a little "beginner" problem:
I have one table called "Clientes" in a MySQL database and using the hibernate
framework I can not save a new object at this table.
No error is reported but the object is not insert in the table.
Bellow is the content of