Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 3158 invoked from network); 15 Aug 2002 15:12:11 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Aug 2002 15:12:11 -0000 Received: (qmail 11895 invoked by uid 97); 15 Aug 2002 15:12:12 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 11868 invoked by uid 97); 15 Aug 2002 15:12:11 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 11856 invoked by uid 98); 15 Aug 2002 15:12:11 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D5BC4AE.5040506@newsguy.com> Date: Thu, 15 Aug 2002 08:11:42 -0700 From: "V. Cekvenich" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020618 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Enterprise Java Beans (EJB) References: <008501c2441d$121c9a80$6e3da8c0@ev.co.yu> <019b01c2441d$70dbd270$0b01010a@powerup.com.au> <1029424108.284.6.camel@wolpert.codeheadsystems.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Consider draping a DAO around your persistence. This way you can replace EJB with JDO or RowSet, should you need to Ex DAO interface: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/basicportal/src_05d/basicPortal/src/org/apache/commons/DAO/BasicDAO.java?rev=1.1.1.1&content-type=text/vnd.viewcvs-markup I found a RowSet implementation of DAO works better than EJB. v. Ned Wolpert wrote: > EJB provides a way to easily encapsulate business logic and reduce > complexity by moving some difficult functionality/designs into > deployment instead of development. Transaction requirements defined in > the deployment of the EJB beans as opposed to part of the development of > the EJB beans. (And they are easy to migrate/scale to many computers > based on deployment configuration, again, making that task easier for > developers since the programmer does not need to do anything special to > achieve this. > > Session beans contain the business logic (Servlets call them) > Entity beans persist the info to the database. (Session beans call them) > Message beans respond to JMS queues/topics. > > In reality, EJB is simply another design pattern... one that was > over-hyped by the vendors, but can provide flexibility needed in some > cases. > > On Wed, 2002-08-14 at 22:34, Josh wrote: > >>Don't suppose anybody can send me a pointer as to what EJB and Jboss >>actually achieve? All i managed to glean from their website were some pretty >>3d variations on the usual "our product in the middle and some arrows" >>diagrams. >> >>-Josh >> >>"Rimmer, real dumplings, proper dumplings when they're properly >> cooked to perfection, proper dumplings, should not bounce." >> >>----- Original Message ----- >>From: "Nikola Milutinovic" >>To: "Tomcat Users List" >>Sent: Thursday, August 15, 2002 3:31 PM >>Subject: Re: Enterprise Java Beans (EJB) >> >> >> >>>>Does Tomcat support EJB?..... >>> >>>No, it is not the task of Tomcat. >>> >>> >>>>if not, is there a project to migrate tomcat to support EJB?... it will >>> >>be >> >>>>a very nice feature... >>> >>>Other servers, like JBoss, are EJB containers, Tomcat can >> >>connect/integrate with them. There is a version of JBoss that comes bundled >>with Tomcat. Take a look at http://www.jboss.org/ >> >>>Nix. >>> >> >> >>-- >>To unsubscribe, e-mail: >>For additional commands, e-mail: >> >> -- To unsubscribe, e-mail: For additional commands, e-mail: