[
https://issues.apache.org/jira/browse/JAMES-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984122#action_12984122
]
Stefano Bagnara commented on JAMES-1184:
----------------------------------------
@Norman about utils as library instead of api, it's not a big deal. as I wrote
it is not something I evaluated well, just wanted to write somewhere a
temporary thought and decided to do it in this public issue instead of a
private note. You answer helped me understand that it probably doesn't worth
touching it (except for the green/yellow classes that can be moved/deleted
anyway).
@Both about nested layers: I agree this need some more thinking and we should
ignore this now. Eric made a good point about looking also to external modules
and organize things from the outside not only focusing on james-server.
about queue modules: I agree that queue management is a bit different from
persistence, but If I understand it well our queues deal with persistence too.
It's not a simple queue but a spool queue. I could implement a file based queue
implementation, or a pure JDBC one (based on the SpoolRepository from james
2.3): our queue is a persistent store where you can put mail and get mails. BTW
I'm not strong on this idea that's why I haven't touch the queue-* modules in
this consolidation..
Thanks for your comments, it's getting exciting again to work on james and to
have constructive discussions! I will probably close this issue soon.
> Modules consolidation
> ---------------------
>
> Key: JAMES-1184
> URL: https://issues.apache.org/jira/browse/JAMES-1184
> Project: JAMES Server
> Issue Type: Task
> Components: Build System
> Affects Versions: 3.0-M2
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Fix For: 3.0-M3
>
> Attachments: graph-server-deps-edited.gif, graph-server-utils.gif,
> graph-server.gif
>
>
> Just opening it to keep track of the proposal to the mailing list.
> ------------
> - mail-file(3)
> - mail-jcr(1)
> - mail-jdbc(3)
> - user-jpa(4)
> - user-file(2)
> - user-jcr(2)
> - user-jdbc(4)
> - domainlist-jpa(2)
> - domainlist-xml(1)
> I only see benefits and no drawbacks in consolidating the 9 modules
> above to the following 4 modules:
> persistence-jpa(6) = user-jpa(4)+domainlist-jpa(2)
> persistence-file(6) = user-file(2)+mail-file(3)+domainlist-xml(1)
> persistence-jcr(3) = user-jcr(2)+mail-jcr(1)
> persistence-jdbc(7) = user-jdbc(4)+mail-jdbc(3)
> - mail-library(1)
> - domainlist-library(2)
> - user-library(9)
> We could consolidate them into a persistence-library module (from 3 to
> 1 module).
> persistence-library(12) =
> mail-library(1)+domainlist-library(2)+user-library(9)
> - queue-library(2)
> - queue-jms(5)
> We could merge queue-library to queue-jms (a library module makes
> sense when we do something useful.. if it is trivial stuff it can be
> duplicated or moved to the api layer).
> queue-jms(7) = queue-jms(5)+queue-library(2)
> -------------------------
> It seems there is agreement on the merging. We still have to decide whether
> to name the modules "persistence-${type}" or simply "${type}" (or maybe
> "data-${type}")
--
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]