This roadmap makes sense to me.
When I wrote it I thought about writing a JDBC Javamail Store because we
already have the specification and we don't need too much discussion,
and using it with your wrapper we could start using it.
But as we already agreed, our hierarchical message repository will be
easier to implement than the whole javamail store "plugin" so maybe it
is safer to do that like you describe.
I think that having a javamail store project would also help us
increasing our community and achieve better/more stable code for the store.
Btw I think that both approaches are valid: I hope I will find the time
to make concretise one of the two as soon as possibile ;-)
Stefano
Joachim Draeger wrote:
Stefano Bagnara (JIRA) schrieb:
We need an ASL licensed JavaMail Store. Better if it uses JDBC.
For testing JavamailStoreMailRepository? I'm planing a lightweight ASL
licensed in-memory JavaMail Store at the moment. This could be very
useful for testing apart from the lack of an ASL implementation.
I see the JDBC based JavaMail Store as a by-product in the future. The
future MessageRepository has to handle hierarchical folders, message
numbers and uids for imap. There will such a MessageRepository that uses
JDBC. It will be quite easy to create a wrapper to JavaMail.... and
abracadabra! There is the JDBC JavaMail Store people have waited for. :-)
I'm looking amused forward to the JavamailStoreMessageRepository that is
for testing backed by a JDBCMessageRepository wrapped in Javamail. :-)
Joachim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
