On 23/10/10 12:54, Eric Charles (JIRA) wrote:
     [ 
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 :)

The last time I commented on such things I went a little wild and spewed a bit too much. I will keep it more succinct this time but it is worth saying.

I think the use of the word 'container' is a really bad term to use for expressing the notion of modern networked software.

If I was to put in my two cents I would say James server is a 'synergistic and empathetic network of components arranged as a modular enterprise mail server'.

Container terminology use is profuse so it might be difficult to use other terms. I do think it would be worth discussing what it 'is' exactly because I think container suggests a particular viewpoint where another might be more appropriate.

Actually, as I sit here writing I might have had an idea, what about 'Cloud of Components' or 'Component Cloud' with all this cloud computing business about at present.

Could it be that James Server is a Component Cloud of type Modular Enterprise Mail Server?

I don't know if that's a joke or if I am actually being serious.

Regards,

Simon

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.


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

Reply via email to