This sounds really interesting - could you elaborate some more on the 5 topics ? (maybe even sourcecode ?)
> For performance reasons we are using only the OJB-kernel (not ODMG, not > JDO), > in combination with a few add'ons : > 1) a 'DisabledObjectCacheImpl.java' to > make the OJB-kernel thread safe So, its up to the programmer to check if they have loaded the same object multiple times as different instances.... (This is not always a bad thing in my opinion) > 2) a few wrappers around the apache - classes Which apache classes ? > 3) a LongTransactionAware - interface for the business objects What does this provide ? And how is it used ? How do you manage locking and transactions ? > 4) a ValidationAware - interface for the business objects What does this provide ? And how is it used ? > 5) a query-engine which uses a repository_sql.xml, which allows > to define complex sql's. What does this provide ? And how is it used ? > My personal opinion is that this is the best mix between > an OO-approach and performance ! Sounds reasonable to me also :) /max -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
