This is obviously trolling but I'll take a stab at actually answering the question, based on the javadoc[0]. (I have never used Spring or JDO and haven't done J

This is obviously trolling but I'll take a stab at actually answering the question, based on the javadoc[0]. (I have never used Spring or JDO and haven't done Java server-side programming since 2002.) The JDO framework has an interface called PersistenceManagerFactory that is used to... well, create objects that manage persistence. Spring has its own thread-bound PersistenceManager abstraction that you need to fiddle with when you're doing transactions. This class lets you use the former's interface but decorated with the latter's behavior, so code that is designed for JDO doesn't need to be modified to call the Spring APIs explicitly. (Am I close??) [0] http://static.springsource.org/spring/docs/2.0.7/api/org/springframework/orm/jdo/TransactionAwarePersistenceManagerFactoryProxy.html http://static.springsource.org/spring/docs/2.0.7/api/org/spr...