Chris, sorry for not responding more quickly... was traveling back from ApacheCon NA.
Honestly, it would be non-trivial to drop in a replacement to Hibernate. The JpaPersistService (http://goo.gl/FeI6xU) handles the configuration coming from persistence.xml and has nothing Hibernate specific. The problem is the CroquetPersistService, DataSourceHibernateModule, and EntityManagerProxyFactory classes. What JPA provider would you rather use? I've never used anything but Hibernate, and never had issues with it... just curious why you'd like to use something else. Also, patches/pull requests are always happily accepted :-) Thanks for checking it out... Bill- On Wed, Apr 9, 2014 at 1:05 PM, Chris Snyder <chris.sny...@biologos.org>wrote: > Looks like awesome work - very clean page design and excellent > documentation, and I'm sure that the quality extends to the code as well. > I'll definitely be looking into this for my next project, if not porting > some of my current ones. > > When using Croquet, how easy would it be to drop in a different JPA > implementation in place of Hibernate? > > Best, > Chris > > > On Wed, Apr 9, 2014 at 12:51 PM, William Speirs <wspe...@apache.org> > wrote: > > > I gave a talk at ApacheCon NA yesterday on Croquet. It is a combination > of > > Wicket, Jetty, Hibernate, and Guice to make it super-easy to start > writing > > Wicket code almost immediately, instead of spending time configuring > > everything. > > > > Slides: > > > > > https://docs.google.com/presentation/d/1m3jdbpYoSBOCPz8Wes9mPvhf8TLp_3dndj_gW08iFL8/ > > Code: https://github.com/metrink/croquet > > Docs: http://croquet.metrink.com > > > > Thanks... > > > > Bill- > > >
