This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi I belive this issue had be raised several times, the use of EJBS has been questioned alot later, the question is when to use EJBs? and what are the benefits you get over using other solutions (stored procedures, JDBC ...), and what will ou lose if you if you went for other solutions?!!
I think you are confusing EJB with Enity Beans. There is nothing stopping anyone from using EJB + JDBC or Stored Procedures. Furthermore, you could even utilize plain JDBC or Stored Procedures from BMP. So it is not a simple either or question. However, I do routinely point out that EJB is massively inappropriate for most projects, especially simple web applications.
Chris, you didnt get my point, what I am talking about is the advantage of using Entiy beans over SP, when we talk about EJB we usually mention "Transactions" ,"security" and "Disributed preocessing". "transactions" : can be achieved in SP with the same simplicity as container managed transactions ...so it is not a big advantage "security" : J2EE only offers class based security which is not suitable for most enterprise applications "distributed proccessing" : looks like the main advantage of using entity beans over stored procedure , but you can alos wrap the stored procedure in a Session bean and you get it. The OO programmer inside me likes the EJBs but how can you convince a customer to pay for such "time consuming" & "exprience requiring= money" EJBs?? Kareem N.Elsayed SCEA part-I, SCWCD, SCJP2 [ September 11, 2003: Message edited by: Kareem Nasser ]