On 2/1/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> but just running probably isn't enough. probably want to be able to
> integrate other services and this is where things become a little more
> difficult. ATM the database implementation uses torque. you'd probably
> want to hack a alternative implementation using JPA POJOs for the data
> binding. maybe could talk to OpenJPA over in the incubator.
Currenlty the database implementation is plain JDBC via
excalibur/cornerstone-datasource services.
Torque is only currently used in trunk as an experimental mailbox
manager backend component.
the spools and so on should be only of interest to james internally.
so there should be no interoperability issues there. yes, mailet
components in the container may want to be fed mail from the spool for
processing and other components may want to post mail onto a spool to
be processed but that should all be black box and so data sources
would be fine.
ISTM that the substantive issue is sharing mailboxes. in other words,
allowing access to a mailbox (a collection of emails for example a
user INBOX) from both james and other container based components. it
would be possible to share objects at the data access level but
perhaps it might be better to expose an interface to allow requests to
be correct scheduled.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
