Hi, I would like to know, if anybody on this list has already accomplished a real project with OJB. My company has (almost) decided to use OJB in one of our current projects (a webbased catalogue and online-shop with about 20000 products where each product consists of 5-20 properties).
Now there are some aspects about OJB which I consider to be rather difficult or which I can't really judge yet. So I would like to hear if somebody has made some _real_ experiences (other then just "checking out OJB") with the following questions: - Is OJB stable enough to handle real projects? (There have been various bug reports on the list, e.g. concerning joins which I consider essential) - How much time does the lack of profound documentation cost? (If you get stuck, sometimes the manual really doesn't go very far. That could cost time and money). - How often do you need a "workaround" due to lacking features? (E.g. lacking capability of mapping one class on multiple tables or not fully implemented OQL). - Has the performance proven acceptable in a real environment even though it is slower than native jdbc? Thanks for any feedback Michael
