We've talked about using hsql or something like that, but I think the issue is frankly performance. I use hsql with great results with small datasets, but James can easily have 1+ gigs in messages and individual messages (a db record) can be 10 megs.Whats about hibernate?
I love hibernate a ton and use it everywhere. However, I think that would be to replace the way we the database repositories. A couple of problems though:
- Hibernate is LGPL, meaning ASF isn't supposed to write code importing it. They've considered publishing their API as ASL-style, but have yet to. Once more, JBoss has effectively bought the Hibernate project, so that complicates matters. As an outside change, the ASF 2.0 license is supposed to be more compatible with (L)GPL, but honeslty I don't know this is relevant.
- Hibernate can generate create-SQL and update-SQL scripts, but it's not always well-optimized. The XML file let's use do very specific create-SQL scripts. Then again, we've got squat for update scripts.
- I think we have people relying on our XML file approach within matchers and mailets... so we couldn't just remove all JDBC code as much as I'd like.
I mean generally I would support anyone with a patch to provide a hibernate mail repository and would support making this the default (or at least preferred over the JDBC one). Just not my itch right now.
One more thought... I've been swearing to myself to build a little web-app to manage my James JDBC mail repositories (delete stuff, move messages around, read what's there, stats, etc...), and if/when I get to that, I would use hibernate and my JSP tag lib I created for it (http://hibtags.sf.net).
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
