Hi all,

I'm working a project using Hibernate 3.0 and Oracle 9i as data store.
Due to constraints, we can only manipulate Oracle data through stored procedures/functions.

As some of you already know, this is not easy, and we had to face some
well known problems such as attributes rotations during objects creation/update, problem with the loader when the object Id is composed of many attributes (themselves issued from many to one relations), etc ...

Facing thoses problems makes me anxious about the reliability of this architecture. Thus my questions are quiet simple.
Is it reasonable to think about production deployment using this architecture ? Is there any people, out there, that used the same architecture on an already deployed production application ?

Answers, return of experiences and/or reflexions are welcome.

Thx in advance

Vince

If you have procedures/functions then it makes sence to generate DAO/adapter code using this metadata (there is no custom data access to develop on JAVA side if you use procedures for everything).