> Or you could petition Sun to open source the reference implementation of JDO > then others can contribute to it & extend it - like they've already done > with Serlvets & JSP (Tomcat) and the standard tag library (JSTL). > > Remember to look out for Castor though I don't think its JDO compatible. > > http://castor.exolab.org/
Castor is definitely not JDO. > Then there's Torque in the Turbine project which is in a similar space, > though not JDO. > > http://jakarta.apache.org/turbine/torque/index.html I suggest that you look into using Torque. It is used as the basis for quite a few projects now for many years, is simple to use and works quite well. All the code generation is done using Velocity templates to output Java code, so they are easily modified. :-) Torque is great because it also does not lock you into using it. If you need to use straight JDBC for something, then that is ok as well...Torque also follows several of Scott Ambler's design principles, such as using an IDBroker. The connection pool for Torque is also integrated into it so that it is 100% database cross platform. You can use Torque to talk to any number of RDBM's and it has support for about 7-10 of the major ones already in it. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
