As you know, there is not much of a "James ecosystem" right now. I am working on and off on a web app to manage James: add/change/delete users, get some stats on the inbox table, delete stuff in the deadletter table, a few other things.
Eric MacAdie
Pronounced: muh-KAY-dee
Norman Maurer wrote:
Hi Eric,
to be hornest I don't think we will preserve the layout of the
database for all components.
For example I expect that the spool will get moved to jms. I'm workin
on this already and hopefuly I will be able to connit the code the
next days.
On the other hand I don't expect the db layout for UsersRepository to
change. The same goes for mailets and matchers that use the database.
For the Users Mailboxes (MailRepository) I would like to find a
solution to reuse some stuff of the imap mailbox stuff. So it would be
easy to switch between Imap and pop3 without the need of copy mails
from one implementation to the other.
Anyway because of that the current Mailboxes are compatible with the
ones in 2.3 , there will at least be some tools for upgrading.
Hope that helps a bit... What layout you are looking at exactly?
Thx
Norman
2010/2/23, Eric MacAdie <[email protected]>:
Will the database schema in James 3.0 be the same as it is now?
Eric MacAdie
Pronounced: muh-KAY-dee
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
