My comments inlined :-)

#: Thomas Ferris Nicolaisen changed the world a bit at a time by saying on  
10/13/2005 12:19 AM :#
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?).


So choose JSF for being a fan instead of a standard? :-). Tapestry is by no means simple and compaired to all named solutions it has so higher learning curve. Considering the Tapestry approach, a much easier solution is Wicket.

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?


Lately there are some moves to support JCR in Spring. A lot of features/requirements of JSR170 can be very easily integrated using AOP (sure not Spring AOP ;-), but as you probably know Spring is integrating very well with AspectJ). Another part of the feature Magnolia feature are also easy to be added using AOP and keeping a simple core model.

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.


I would say that using Spring will not be an immediate benefit of Magnolia core, but it will create various possibilities to extensions.

Remember the golden rules:

-Build what you know.
-If it works, don't mess with it.

Are you sure these are golden rules? :-)

take care,

./alex
--
.w( the_mindstorm )p.


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to