Simon Funnell
Thu, 26 Nov 2009 09:14:14 -0800
Hi,Thanks, I have the latest code base and have been taking a look around. I have also been looking at JSR250 and OSGI. If version 3 is well on its way it is probably best I look towards version 4, which attempts to refine existing feature definitions for the purpose of adding management services. This will allow me to continue working on documentation without disturbing anyone else as you can look at it any time over the next month :) don't be surprised if I go berserk (in the sense of ruthless).
Regards, Simon Norman Maurer wrote:
Hi Simon, first of I can't give you feedback for the wiki pages because I had no time yet to read them. But I will come back to you later ;) About the release date.. I think I will try to get all things done for a milestone when I have complete the avalon -> guice move, which should be within the next month. To complete this I will lookin into replace phoenix with osgi as proof-of-concept for using OSGI. Bye, Norman 2009/11/25 Simon Funnell <simonfunn...@googlemail.com>:Hi, I've been working on a few wiki pages and feel as if I am at a juncture. I've been looking at the version 3 code base (rather than version 2...) and getting a better idea of the big picture. I would like to expand the documentation further but would like some feedback as to whether they are appropriate descriptions. It's a little bit sketchy and there are a few things I have missed because I haven't had time to look them up yet, but I think its fairly comprehensive. I think the JamesUserTypes is important because this is how I currently view/manage James (and other projects). http://wiki.apache.org/james/JamesUserTypes http://wiki.apache.org/james/JamesTools http://wiki.apache.org/james/JamesArchitecture James weakest point, and something I would certainly like help to improve is the Administrator services, which are basically, very minimal. I think its important to stress that large parts of the configuration, basically the mailet configuration and related items, while it is a configuration, it is more importantly a organisation/business application. This aspect of the configuration changes regularly and needs to be deployable, like a web application. The version 3 code base is much better and has encouraged me a lot, there is a lot more reusable stuff. It has also convinced me that Platformed can be of significant benefit to James. Platformed is not comparable to Guice and unfortunately a lot of inversion of control containers are indeed injection frameworks. Platformed is not an injection framework, it is a multi-threaded server application framework and it uses, amongst other things, injection. At this stage, I am still happy to create documentation in a non-obtrusive manner as this will allow me to offer more constructive propositions. Is there an expected release date for version 3? Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org