2. I would wrap a custom exception around the HibernateException. This would further enforce the client/service to code to the interface, thus further hiding the fact that you you are using Hibernate as ORM. So if you change to a different ORM, the client code will not change.
Joined: Mar 19, 2002
My mistake forgot the last part ...
Joined: Feb 08, 2004
i got the idea thanks a lot!
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com