>PersistenceProvider is an interface and the implementation class >doesn't depend on Spring at all. It's a pure hibernate DAO, >essentially. The example application is pieced together with Spring, >since that's what I'm familiar with and it allows me to put something >together with little effort by copy/pasting stuff from other projects >that I know work.
We created and maintain the open source persistence abstraction framework called exPOJO (expojo.com) than can support any persistence technology under the hood upon which your application (or indeed other framework) can with be written with no direct reference to any specific framework (Hibernate, JDO, JPA). Currently JDO and Hibernate plugins are implementated but JPA could be easily accommodated via the same interface. It allows you to write applications where the UI and model need have no direct reference to any specific framework - keeping your app "persistence framework agnostic". Following Chris Richardon's 'Exposed domain model' pattern it works with repositories and service classes. It is only the repositories (collections of query methods) that need to be written in a specific persistence framework's query language. The rest of the app can remain blissfully independent and portable and usable by developers of any ORM persuasion. The coincidence here is that we also have a class called PersistenceProvider which is the abstract interface that you write your app (or framework) to. >We get it, you don't like Spring. :) He's not the only one! In addition to 'abstracting' the persistence framework exPOJO provides an optional dependency injection mechanism which provides virtually automatic OpenSessionInView/OpenPersistenceManagerInView without needing the multimegabyte bloatware that Swing has become. exPOJO is uber lightweight: a 35k jar, 30 minute learning curve etc., that is completely XML free and typesafe. > >> Also, does wicketopia depend on Spring? That would be a really *really* >big downside. I don't need any frontend library telling me what >persistence framework to use, and Spring is about much more than just >persistence. Abstract that stuff. >> > >Again, no. Take a look at the pom.xml files: > >https://wicketopia.svn.sourceforge.net/svnroot/wicketopia/trunk/pom.xml >https://wicketopia.svn.sourceforge.net/svnroot/wicketopia/trunk/persistence >/pom.xml >https://wicketopia.svn.sourceforge.net/svnroot/wicketopia/trunk/hibernate/p >om.xml >https://wicketopia.svn.sourceforge.net/svnroot/wicketopia/trunk/jpa/pom.xml > >There are modules that depend on Spring (spring-security and >domdrides), but you don't have to use them. > >> Perhaps when I can understand what Wicketopia is without having to UTSL, >I'll consider giving it a try. Assuming I don't also need to suffocate my >code under the weight of Spring. >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
