> [...] > The Spring framework's Java-Bean approach is IMO a way better > solution to the POJO-ification issue. > > Now I have started to convert James into POJO's the Spring > way (only James.java so far), but as I stated above I hate > doing things over, so let us take a vote. Is it going to be > SpringJames or JamesNG. > > I will start with a +1 for SpringJames.
You should better define the roadmap for what you are calling SpringJames. Making "setter driven dependency injection" POJO's from the current components and inject cornerstone components? I've looked at JamesNG sources and I found it is a completely new project: pratically no code in common with james. I'm not a committer but I think that the person that will have the time to do this major change should take a few hour to update the issue site and apply old patches BEFORE major updates. I also think that a 2.2.1 release should be made available BEFORE any major update. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
