On 2/20/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
Dave wrote:
> 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
I refuse to believe this is a JPA thing. it has to be something with
the way you are using weblogs and categories which is broken because
it's obvious that the websiteid for a category should never be null. We
have other associations which are exactly like this (folder, weblog
entry) which should be broken as well if this was really a JPA issue.
I didn't really mean to imply it is the fault of JPA, but it
definitely an open issue in the current roller_4.0 code base that
needs to be fixed.
> - Open issue: some parameterized queries should be cleaned up
In general, my feeling about the new Datamapper/JPA backend is that it's
more confusing and difficult to understand and work on than the current
Hibernate backend. Parameterized queries are definitely one part of the
problem.
> 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
This one actually scares me a little bit. I have been operating under
the assumption that the Planet application can be worked on and progress
on a different schedule than the Weblogger application and they don't
need to be tied together.
I think we need to be a little careful about promoting the changes in
the Planet app to be used by Weblogger until things have stabalized.
I agree that Roller and Planet can be on different release schedules,
but I don't think it's acceptable to be stuck at Roller-Planet 3.1
level in Roller 4.0.
- Dave
