+1, I've been wanting to remove PersistentObject for quite a while.
I'm not sure exactly how #1 affects #3 since Planet and Weblogger now of isolated backends, but you are correct that the Planet app needs its own JDO/JPA backend impl now.
The other good thing about this is that it will require some better implementations of equals() for various pojos, which is something that I think we've needed for a while.
-- Allen Dave wrote:
I'm working with Craig and Mitesh this week, helping to get their JPA implementation up and running. I'm running into some issues: 1 - The JPA implementation doesn't include the new Planet interface 2 - The Planet POJOs no longer extent PersistentObject 3 - The Roller POJOs still do Working on code for #1 I've found that #3 makes things a little painful. So in my workspace now, I'm working on eliminating the PersistentObject class entirely and replaced the kludgey store() and remove() code in HibernatePersistenceStrategy with nice clean implementations (like the one in Planet's strategy). Any objections to eliminating PersistentObject? Any other ideas or suggestions? - Dave
