Trim all your mails, darnit! :)
JSF is a personal favourite of mine (being a R. Hightower fan and all), but
still, SpringMVC (a web-framework) has been very well spoken of lately. Webwork
has always been the healthiest option, while Tapestry is more simple and
web-design friendly. Don't choose JSF because it's a standard (EJB2 anyone?).
Conclusion: This is a descision you should not make without having tried the web
frameworks yourself!
Using Spring (container) for Magnolia's internal architecture would force a
huuuuge amount of refactoring (or so I can imagine), for what? Inversion of
control? JSF's backing beans provide basic IoC. And does Magnolia really need
IoC? Does it need AOP? Why?
I can really see the value of being able to plug in new datasources and be able
to choose between web frameworks (that you can plug into Spring), but I'm not
sure the devs are ready for such changes.
Remember the golden rules:
-Build what you know.
-KISS
-If it works, don't mess with it.
-Don't believe the hype.
-Try before you buy.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
