Hi Emma, This is how it works.
You will need also to look at the different spring files spread in the other modules. These are responsible to inject the beans. Load the all the server module in your favorite IDE http://james.apache.org/server/3/dev-build.html The modules are usually built upon a api/library/impl pattern. The unit tests are also a great place to start. Have a look for example at the data-file: try to understand how the injection is made and run the tests. You will also need to understand the difference between the mailbox persistence and the mail repository (that's something we need to remove, but we have to live with it for now) http://james.apache.org/server/3/feature-persistence.html Hope this helps, Eric On 04/25/2014 05:29 PM, Emma Sesmero wrote: > Hi all, > > Currently I am studying how james is run, how it starts, to be able to add > Bond in the process, so it can start at the same time when it deploys. > > I have checked the class JamesAppSpringMain, that, if I am not mistaken, is > the start point, and seen the > file META-INF/org/apache/james/spring-server.xml with the files imported > for each server that start with james. > I have seen that it uses the Spring framework, so I am working on becoming > familiar with it to be able to understand better how it works to be able to > modify it and add the Bond deployment to it. > > I was wondering if any of you has a better understanding of how this works > exactly and might be able to give me a hand. > > Thank you very much in advance. > Kind regards. > > Emma > --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
