Folks,
This generalized architecture question that is not specific to Jboss, so
please forgive me if its inappropriate in this forum.
I am involved in architecting a 3-tier system using JBoss as the app server
and Oracle as the database.
I am working for an Oracle shop who are new to J2EE and they have a
preference for placing the business logic in stored procs so that they can
leverage their existing expertise.
i.e. The app server hosts SessionBeans's that simply delegate to stored
procs.
The standard approach, as I understand it, is to place the business logic in
Session EJB's and use entity EJB's and Data Access Objects to model the
database rows.
Does anyone have any opinions or recommendations regarding each approach?
What are the advantages/disadvantages of placing the bus. logic in the
middle tier as opposed to the database?
Assuming the bus. logic is stored in SessionBeans, what are the advantages
of using entity beans to model the database rows rather that hitting the
database direct from the SessionBeans?
Any opinions would be gratefully accepted....
Thanks - Adam
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
