We are planning a November 2003 production deployment with OJB and WE LOVE IT!! We have been in development on a very data-centric application in the power industry for about 5 months now and OJB has undoubtedly saved us countless hours of development time. We have received benefits in the following areas:
-> Easily adapts to any data model that we've thrown at it. No problems mapping tables with compound keys, tables mapping polymorphic relationships, identity columns, etc. -> Seemlesly switches between target DB platforms. We develop and unit test on our local workstations with HSQLDB and PostgreSQL, and deploy to DB2 using the Type 4 JDBC driver from IBM. Works great! -> Makes querying a breeze with the PersistenceBroker API Overall we have found OJB to be very stable (and we've really tested it out quite a bit). The only issues we've got outstanding at the moment is support for connections to multiple databases, but I've noticed in CVS that the OJB guys are already fixing this for OJB 0.9.9. Anyway, just wanted to share our experience. -- Jason ----- Original Message ----- From: "Jason McKerr" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Friday, January 31, 2003 2:11 PM Subject: Re: Is OJB stable for production? > Hi Haytham, > > We're using OJB in two production applications at the Northwest Alliance > for Computational Science and Engineering (NACSE). One is a data mining > toolset, and the other is a massive National Science Foundation project > that involves huge amounts of data, and about 20 or 25 universities and > research groups like mine. > > In fact, I've begun making OJB sort of a de-facto standard for NACSE > java/database development. I've thrown out EJB's for the most part and > I've tried JDO from Castor, but I'm sticking with OJB. Maybe we'll > reconsider JDO when the OJB implementation is more complete. > > -Jason > > On Fri, 2003-01-31 at 11:03, Thomas Mahler wrote: > > Hi Haytham, > > > > Haytham Samad wrote: > > > Hi all, > > > > > > I am new to OJB and very interested in using this tool in a new project that > > > I am working on. I was just wondering how I can get information about OJB's > > > performance and whether or not it is ready for production use? > > > > OJB is used in production application since version 0.5. We have about > > 6.000 download each month and a wide user base using it in a large > > variety of production scenarios. > > > > We provide a regression test suite for QA. You can use this testsuite to > > check if OJB works smoothly in your target environment. > > (see ) > > > > We also provide a performance testsuite that compares OJB performance > > against native JDBC. This test will give you an impression of the > > performance impact OJB will have in your target environment. > > (see ) > > > > > > > Are there > > > any aspects of OJB that still need improvements that I need to watch out > > > for? > > > > I regard the core functionality for quite stable. If you follow the mail > > archive you will see that severe bugs are very rare. Bugs are often > > fixed within few hours. I don't know much commercial vendors with such > > short response times... > > > > But: > > > > - We don't have cool graphical mapping tools yet. Our forward- and > > reverse-engineering tools are not yet perfect. This is certainly an area > > where we have to improve. > > (Most developers are happy with editing a simple xml based mapping > > repository) > > > > - Currently we don't have our own JDO implementation. We are providing a > > simple Plugin to the JDO reference implementation. By using Sun's JDO > > Reference implementation and our plugin you have a full JDO compliant > > O/R mapping tool. But it's no ideal solution, at least from a > > performance point of view. > > A full JDO implementation is in Scope for OJB 2.0. > > > > > > > Can I replace those parts with something else? These answers will > > > really help me make a decision quickly since time is an issue. As you have > > > realized I am new to OJB and your patience and help is appreciated. > > > > I hope my answer was fast enough :-) > > > > cheers, > > Thomas > > > > > > > Haytham > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]