[
https://issues.apache.org/jira/browse/JAMES-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032063#comment-13032063
]
Stefano Bagnara commented on JAMES-1237:
----------------------------------------
I can't find @Inject annotations in the mailbox source tree.
About transactions I'm not sure I understand your concerns.
I don't see the way a spring or guice module will help too much developers for
mailbox (instead I believe there is much to do in this regard in java code
instead), but anyway you proposed separated modules so in the worst case it
won't hurt. So go ahead, I will be happy to review the code and I hope to be
surprised :-)
> Reorganize system configuration files (spring context, xsd)
> -----------------------------------------------------------
>
> Key: JAMES-1237
> URL: https://issues.apache.org/jira/browse/JAMES-1237
> Project: JAMES Server
> Issue Type: Improvement
> Components: Deployment Modules
> Reporter: Eric Charles
>
> There is a trend for configuration/properties files to be placed in META-INF
> (look at cxf, camel, maven,... distributions).
> Also, I think the injection of dependent project (mailbox, imap) should not
> be defined in server, but in the project it self.
> We could have the same approach and define a META-INF/james to hold those
> files
> The server context could go to META-INF/james/server-spring.xml, and we could
> move the definitions related to mailbox,imap to their respective project
> (with the same strategy, in META-INF/james/mailbox-spring.xml,...)
> For the embedded XSD I'm not sure if thy need to go to
> META-INF/james/org.apache.activemq,... or META-INF/activemq/
> In all cases, the user can stilll override the defintions at deployment time
> simply by defining the files in the conf folder (conf is on top of the
> classpath).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
