Hi Simon, first of nice to hear you are interested in James :) I already started to replace many Avalon dependencies from the components of James. The current Idea is to replace Avalon with Guice for DI. We use Guicey-fruit to support JSR250 for dependency Injection which provides at least some "standards".
At the moment I do this step by step by providing some kind of Adapter between Avalon and Guice to allow the "smooth" migration. Have a look at the AvalonAsyncSMTPServer for example to get some idea about how it works atm: http://svn.apache.org/repos/asf/james/server/trunk/smtpserver-function/src/main/java/org/apache/james/smtpserver/mina/AvalonAsyncSMTPServer.java All the "Avalon*" classes will get removed when every component is rewritten to work with Guice (jsr250). As Container I'm currently lookin at karaf (http://felix.apache.org/site/apache-felix-karaf.html). Not sure if this is really the way to go. So any feedback / sugguestions are really welcome, and feel free to ask more questions :) Bye, Norman 2009/11/15 Simon Funnell <[email protected]>: > Hi, > > I've been using James for a couple of years now and enjoy the service it > provides, I actually use quite a few things from the Jakarta project. With > the development of version 3 I have become interested in integrating James > with an existing server framework I have been developing. On the wiki > homepage it discusses moving away from the Avalon framework and I am happy > to contribute code I have written should it be useful. I read elsewhere on > the wiki that the terminology surrounding the ideas of > containers/micro-kernels/etc is a bit vague and this is actually some of the > issues the framework addresses. I was wondering if someone can provide me > with a brief list of requirements for a James container and/or any > information/links to documentation that discusses the subject. > > Thanks, > > Simon > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
