On Mar 5, 2006, at 8:11 PM, Matt Raible wrote:
I think Spring is great for assembling applications, but for something like Roller that's practically "feature complete" - I don't know that it makes a whole lot of sense. Then again, if Roller's backend is difficult to test or maintain - using Spring would likely solve that. I would say the decision to use Spring vs. don't use Spring should like with the folks that work on Roller the most - which is you and Dave. It sounds like neither of you are very enthusiastic about using it - so my recommendation is simple. Don't. ;-)
True, but Anil is enthusiastic and willing to make a specific proposal. If it makes Roller easier to test, maintain or customize then it's worth considering pulling in other parts of Spring.
Spring is a collection of frameworks and utilities and we're already using some of that now. Plus, we're shipping the complete spring.jar with Roller (so we can use Acegi).
So, my first reaction -- "not another framework" -- was really about Spring MVC. We already have a Web/MVC framework. If I thought a using a framework instead of our page servlets would improve Roller (maybe it does), I would be investigating the new Struts2/WorkWork stuff. That should (?) be the easiest migration path for our existing Struts UI and couldn't it do pretty much the same things as Spring/MVC for our page/feed rendering code? That's an honest question -- I don't know the answer.
- Dave
