Originally posted by Ken Krebs:
If it sounds like I'm selling, I guess I am as I am one of the gang of 12 although my contributions have been very small...
I hope you'll give it a closer look.
Originally posted by Carleton Harrison:
- production apps?
-- There are 12 developers - as compared to the huge infrastructure behind behind other products (J2EE RI/Tomcat/Struts/JRun/ etc...)
-- It is still in Beta
-- It has only been around for a little over a year
-- Not universally accepted yet
Just some thoughts...
Most successful projects (Hibernate for eg) have a small number of core developers, as Rick pointed out. We have lots of people approaching us who want to be Spring developers, but I would rather keep the number of active developers small to ensure quality and focus. (There will likely to be a number of spin-off projects, however, such as the alpha Eclipse plugin project.)
Having a clean, elegant concept is key to the resources you require. Take Hibernate and CMP. It takes an army to implement CMP and the results are...well my views on this are well known :-) Whereas Gavin implemented the core of Hibernate largely himself, and it's great.
Spring 1.0 final will be released in February. RC1 is due out next week.
Spring is used in production in numerous applications including banking applications.
But when considering using Spring with Struts, it's important to remember that the alternative is usually to manage the middle tier via some home-grown mechanism: like ad hoc singletons, hand-rolled service locators etc. With Struts alone, the MVC layer is well-proven, but a whole lot of your stack is in-house because Struts doesn't aim to help you in the middle tier.
With Struts+Spring you get a solid, well-tested middle tier solution that means you write a lot less code. And because Spring imposes minimal dependencies on your object model, you don't have to write a whole lot of Spring-specific code.