Here's some status of the work in the roller_4.0 branch:
a) Datamapper / JPA backend has been promoted - It's been moved from sandbox and into main source directories b) Datamapper / JPA passing all but one test and UI is working - And I'll be working to keep it in-sync with the Hibernate implementation - Open issue: JPA wants weblogcategory.websiteid to be nullable - Open issue: some parameterized queries should be cleaned up c) Roller-Weblogger UI updated to work with new Roller-Planet data model - Roller UI now assumes that there is one default Planet object - Roller UI now uses Planet PropertiesManager instead of PlanetConfigData d) components/core Module created - For code that is shared in both Roller-Planet and Roller-Weblogger - Right now this is only the core persistence classes - Like Planet, we build core separately and commit the jar to SVN - (see tools/roller-core/roller-core.jar and tools/roller-planet/roller-planet.jar) e) roller_4.0 branch is in sync with trunk as of today - And I'll be working to keep it in sync until we're done with 3.x releases - Beware: createdb and 3xx-to-400 migration scripts are in flux right now f) Started Struts2 migration, in anticipation of Struts2 UI work in 4.0 - Struts2 jars now included in build - Struts2 filter now included and mapped Comments, objections and suggestions are welcome... Next I plan to work on open issues in (b) and do some JMeter testing (and possibly some profiling) to compare the JPA and Hibernate implementations. - Dave
