james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joachim Draeger ...@joachim-draeger.de>
Subject Re: [jira] Created: (JAMES-521) Mail/Spool/Message repositories refactoring
Date Fri, 02 Jun 2006 20:05:32 GMT
Stefano Bagnara (JIRA) schrieb:

> - Introduce a MessageRepository interface for MimeMessages (not Mail objects) to replace
the current MailRepository usage: we could even use JavaMail Store/Folders but maybe we should
have our own interface and a wrapper.

The biggest design deficiency of Javamail is the lack of interfaces. That's why 
using javamail means being limited in hierarchy, and being unable to completely 
replace implementations.
Because we need only a subset of the Javamail capabilities it maybe better to 
concentrate on the main requirements.
On the other hand we should always keep Javamail in mind to make a compatibility 
layer possible.
There are also efforts made implementing Javamail for Apache. I think Geronimo 
needs it to be fully JEE 1.4 compliant? Maybe it is an option not to use 
Javamail API 1:1 as storing layer but share some code with them

>   - MessageKey created while storing, and not userprovided.

This would make implementation of existing standard a lot easier. Are there 
disadvantages? When I store the same message into different repositories I've to 
care about the repository keys myself when I want to access them again. Instead 
of using my own. Does this happen in James reality?


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message