I would be inclined to agree on the OODBMS statement. Another reason might be vendor instability. I once worked with a group that actually built a product using the Gemstone/J app server and now Gemstone is discontinuing that product. This is obviously not very pleasant. I do like the idea of using the OODBMS as a caching mechanism for high traffic J2EE systems that still require some caching complexity as well.
> >I am somewhat familiar with object databases and (no offense) would stay >away from them for query-intensive apps. The main trouble with odbs is >pretty much the same problem I described re: OO paradigm above. It needs >to >realize the entire object. So, if I want to project and join, etc. (which >are all value-based operations), it falls flat on its face. If you need to >manipulate the data and partition processing of data between client and >server, odbs don't perform. If your objects don't need manipulations like >projection and join, it works well. > > >Atong > > >> >>Why use EJB? You may or may not need it. Atong, you might want to >>explain >>your application in further detail, and get feedback on EJB's >>applicability >>from the list. It's difficult to discuss the generic benefits of EJB >>beyond what you will find on Sun's web site. A specific project >>discussion >>would make an interesting thread! >> >>[clip] >> >> >>Tom Groot _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com =========================================================================== 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".
