Personally I've reservations about JDO. I spent some time evaluating Kodo's implementation last year. I was initially very enthusiastic, but found persistence was not so transparant when dealing with transactions. I found myself wrapping PersistenceManager functionality in a singleton to try and reduce the persistence framework pollution. It just didn't feel right for something that was touting transparant persistence.
Also, I came across the posting on CocoBase's website regarding JDO. Its very biased toward CocoBase but some of the points are quite interesting. http://forum.thoughtinc.com/showthread.php?threadid=144 If you want a Rolls Royce solution, why not try TopLink? :-) http://www.webgain.com/products/toplink/ Ed. _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
