[
https://issues.apache.org/jira/browse/JAMES-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924181#action_12924181
]
Eric Charles commented on JAMES-1074:
-------------------------------------
Hi Norman,
If we want to let the door open to use james without a "container" (=injection
+ lifecycle impl), yes, lifecycle-api would be the way to go.
But i don't see how we could let james work without a kind-of-container.
MimeMessageWrapper is util, MailImpl is not util nor container, so you're
right, we need some kind of core.
I wonder if we could get rid of this intermediate MailImpl and directly use the
Mail from Mailet project.
But of course, this would introduce a direct dependency between the server and
the mailet, something that would not be needed if someone wants to gives access
in read only to the mailbox.
The MailsServer/SpoolManager: to be rethinked with a copter view and with that
stupid question: "what's a James server?"
True, we don't need some container-api for the different container-*
Tks for your feedbacks :)
> Align packages hierarchy of the services
> ----------------------------------------
>
> Key: JAMES-1074
> URL: https://issues.apache.org/jira/browse/JAMES-1074
> Project: JAMES Server
> Issue Type: Improvement
> Affects Versions: 3.0-M1
> Reporter: Eric Charles
> Assignee: Eric Charles
> Fix For: 3.0-M1
>
>
> We need to align package service hierarchy to have stable api, uniformity and
> osgi-deployable.
> For example, the proposed hierarchy for a "mail" service is:
> org.apache.james.mail.api (in the mail api project)
> org.apache.james.mail.lib (in the mail library project)
> org.apache.james.mail.jpa (in the mail jpa impl project)
> org.apache.james.mail.jcr (in the mail jcr impl project)
> ....
> The conf files and spring-beans.xml need to be updated according to the
> repackaging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
