Re: Guice vs. Spring

On 18/05/2020 16:23, David Leangen wrote: >> But maybe all of this should be discussed in a separate thread as a >> "Guice roadmap"… > > These all seem like great ideas to me. > > I just had a wild thought based on your ideas. Just like there is a concept > out there of “headless CMS”, maybe

Re: Guice vs. Spring

> But maybe all of this should be discussed in a separate thread as a > "Guice roadmap"… Good idea to discuss this in a separate thread. In the meantime, I will continue down the path I mentioned here: https://www.mail-archive.com/server-dev@james.apache.org/msg65771.html

Re: Guice vs. Spring

> But maybe all of this should be discussed in a separate thread as a > "Guice roadmap"… These all seem like great ideas to me. I just had a wild thought based on your ideas. Just like there is a concept out there of “headless CMS”, maybe we could have some concept of a “headless enterprise ema

Re: Guice vs. Spring

On 18/05/2020 14:35, Matthieu Baechler wrote: > On Sun, 2020-05-17 at 14:32 +0900, David Leangen wrote: >> Hello, [...] >> I think Guice is easy enough that it would be worthwhile for me to >> learn it, even if it’s just for James. >> >> On that note, what are the plans going forward regardin

Re: Guice vs. Spring

Thank you very much for the reply. >> Should I even bother learnings about Spring? > > No. Ok, in that case I think it is clear that I should just ignore Spring while developing the documentation. Honestly, I think we should just avoid all mention of it all together. All it will do is requ

Re: Guice vs. Spring

On Sun, 2020-05-17 at 14:32 +0900, David Leangen wrote: > Hello, > > [...] > Why are there two frameworks (both Guice AND Spring) instead of just > one? Don’t they basically accomplish the same thing? Of course, they even share annotations with `javax.inject`. It's two implementations for a sa