I just posted the following reply: "OJB is a nice small product and they recently joined Apache, it seems to be an active project."
Small compared to what? Our distribution is about 7MB. The framework consists of about 600 classes and a regression testsuite with about 200 classes. In fact we are an active project with 1 - 2 public releases per month! "Unfortunately they rely on the dead ODBMG standard." Not true. OJB provides multiple user APIs. A kernel API (called PersistenceBroker API), an ODMG 3.0 compliant API and a JDO 1.0 compliant API (this not yet feature complete). Do know of any commercial O/R with such a rich API set? When OJB started, JDO was not yet specified. thus we started with an ODMG interface first. In what sense is ODMG dead? What features of the JDO API do you miss in ODMG? Supporting ODMG is extremely useful for projects that need integration with OODBMS and RDBMS! "They announce some kind of JDO support, but I'm afraid it won't happen before a long time." Wake up! It's already there! We even have a complete JDO tutorial that demonstrates how to use the OJB JDO implementation! "OSS products are a good bargain if you don't have hard QoS constraints. They generally focus on features rather than on robustness, stability, scalability," Not true for OJB! We have a regression test suite with more than 220 TestCases . We are even shipping this regression testsuite with our binary and source distribution to allow users to check if there could be any problems with their target database of choice. We also provide a Performance Test suite that allows to evaluate if OJB provides sufficient performance in high load scnenarios. Do you know of any commercial product that publish their regression testbed and their performance tests? We are realling taking QA serious. OJB is meant for mission critical applications, so users must be provided with means to ensure quality! OJB ships with a highly scalabale client/server architecture. It's possible to run an OJB clusterered server on on multiple VM's on multiple physical. We also have a distributed cache... "but you can still develop yourself all these features if you want (but just compare the time spent with the cost of a supported commercial product)." Not necessary with OJB... I give a short example: In my company we have been using TopLink. For a mid-range project we had to pay about 100.000 EUR (developer and runtime licenses). Since half a year we are using OJB for all new projects. Works great even for mission critical apps! No problems wrt. to QoS aspects (robustness, stability, scalability)! And it safes us several 10.000 EUR per project! Matthew Baird wrote: > http://theserverside.com/home/thread.jsp?thread_id=15312 > > unfortunately I don't have a login on TSS (and I refuse to get one) to counter the >FUD regarding OJB. > > m > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
