Servlets.com

Home

What's New?

com.oreilly.servlet

Servlet Polls

Mailing Lists

List Archives

Servlet Engines

Servlet ISPs

Servlet Tools

Documentation

Online Articles

The Soapbox

"Java Servlet
Programming,
Second Edition"

"Java Enterprise
Best Practices"

Speaking & Slides

About Jason

XQuery Affiliate

Advertising Info

Poll Comments
Have you used Enterprise JavaBeans (EJBs) to support your servlets on a production site?

The following comments have been recorded for Yes, and it went well

  • 1 (16 Nov 2016 00:00)
  • 1 (15 Jun 2016 00:00)
  • A million thanks for posting this inaofmrtion. (6 Jan 2016 00:00)
  • For the love of God, keep writing these arscelit. (17 Oct 2015 00:00)
  • Yes we did on 888.com (16 Apr 2015 00:00)
  • 1 (31 Jan 2005 00:00)
  • I like to use EJB (7 Oct 2003 00:00)
  • Stateless session only... (9 Nov 2001 00:00)
  • Sun should give JBoss a free J2EE Compliance Test Possibility (4 Nov 2001 00:00)
  • We have use EJBs but I dont find the need to use Session Beans because we dont need any container services such as transaction management, security, etc (31 Oct 2001 00:00)
  • EJB is the legitimate distributed business component in Java. (29 Oct 2001 00:00)
  • Overkill is only applicable when you don't have anything significant to do! Entity Beans are worthless. Session Beans are cool. (26 Oct 2001 00:00)
  • session based entity based seems to have more limitations than expected (26 Oct 2001 00:00)
  • Well, it went okay. Some problems with the deployment. Did appear to be a little overkill though. (26 Oct 2001 00:00)
  • because its the best (25 Oct 2001 00:00)
  • We actually wrote the EJBs first as part of our client-server application and then added a web app on top of them. (25 Oct 2001 00:00)
  • EJB were used for data retrieval from Oracle and DB2 with some 2 pahse commit. After ironing out some problems, it appears ot scale well. We still have some issues but don't know if it relates to the EJBs or the database. Another plus with EJBs is that they can be accessed without modification from remote clients using JNI. We are presently using WebLogic Server 6.1 (25 Oct 2001 00:00)
  • Far more efficient than a native JDBC approach. (25 Oct 2001 00:00)
  • Mainly stateless session beans. (25 Oct 2001 00:00)
  • they are pretty annoying with tomcat (because of reloading classes) but necessary for some jsp stuff (25 Oct 2001 00:00)
  • Session EJBs are the most useful, Entity only for complex data. If you have a good project they're very useful and performant, otherwise they are useless and elephantic. (25 Oct 2001 00:00)
  • They work great for transaction support (24 Oct 2001 00:00)
  • we're using two-phase commit. so EJBs are a must. (24 Oct 2001 00:00)
  • EJBs Yes. No Servlets required! (24 Oct 2001 00:00)
  • It was overkill. (24 Oct 2001 00:00)
  • they are often over kill however (24 Oct 2001 00:00)
Back to Results

 


Home   com.oreilly.servlet   Polls   Lists   Archives
Engines   ISPs   Tools   Docs   Articles   Soapbox   Book

Copyright © 1999-2005 Jason Hunter
Privacy Policy

webmaster@servlets.com
Last updated: March 1, 2009