I have been playing with some ~JDO's lately with the IBM "Data Access Beans" that come with Websphere. The advantage I see EJB's having here are that they are running in a container where common services can be provided across an organization. The JDO's are standalone in a sense where I could see each group in a large organization developing their own frameworks/containers to handle them. At this juncture, why not just use the EJB container rather than writing one yourself?
>From: Andrea Vicentini <[EMAIL PROTECTED]> >Reply-To: Andrea Vicentini <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: WHY EJB >Date: Thu, 18 Oct 2001 03:28:42 -0700 > <snip> > >If we're looking into good OO design, what about JDO? > > </snip> ... _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
