| **DONOTDELETE** |
| (Unregistered) |
| 01/21/08 10:20 AM |
Re: J2EE design decisions
|
I don't totally agree with your points...
1.) You are using stored procedures.. that probably have business logic build in them, then you are replicating your business logic both in your java code and sql... and probably you need to rewrite the validation code.. any change in business logic will take your double efforts.
2) Writing SQL procedures is quick...agreed..but debugging? --- even harder than java... and if database has inconsistent data .. the stored procedures can not provide exact error... if frameworks like Hibernate is used, we can enforce integrity constraints easily..
3) Yes SQL is written by DB specialist, but sql will be executed by JDBC call only.... any small mistake can cause java code to break and complete transaction is gone..
4) ok
5) We all need to support.... if you leaving your company after coding then the persons who joins later have to mess up with divided code...