另请记住，当涉及太多 Spring（或任何其他 ioC 容器）时，有时（8-12 个月后）您将无法正确调试代码，因为涉及的类太多，您只需保留 最后，正如我的一位导师常说的那样，不要解决世界问题（通过使用大量设计模式），而是
解决手头的问题。 :-)
I would consider what is the scope of my project, if I am anticipating complex system with lots and lots of various implementations, then I would go for Spring, for moderately complex system I would go for JSF.
One also need to consider if the primary designer leaves the team would other team members or a new comer will be able to pick particular MVC framework with ease or not (consider using well known MVC vs not-so-well-known-personal-favourite-picked-out-of-google). How mature the particular MVC framework is, are there good books written about it etc. These are just from top of my head.
Also keep in mind when there is too much of Spring (or any other ioC container) involved, there comes a time (after 8-12 months) when you are unable to debug code correctly because there are so many classes involved that you just keep tracking which class goes to which spring context files etc.
Finally, as one of my mentors used to say, don't solve the world problems (by using lots of design patterns), solve the problem at hand. :-)
发布评论
评论（1）
我会考虑我的项目的范围，如果我预计复杂的系统有很多很多不同的实现，那么我会选择Spring，对于中等复杂的系统我会选择JSF。
还需要考虑如果主要设计师离开团队，其他团队成员或新来者是否能够轻松地选择特定的 MVC 框架（考虑使用众所周知的 MVC 与不太知名的个人最喜欢的框架） -从谷歌中挑选的）。特定的 MVC 框架有多成熟，是否有关于它的好书等等。这些只是我的想法。
另请记住，当涉及太多 Spring（或任何其他 ioC 容器）时，有时（8-12 个月后）您将无法正确调试代码，因为涉及的类太多，您只需保留 最后，正如我的一位导师常说的那样，不要解决世界问题（通过使用大量设计模式），而是
解决手头的问题。 :-)
I would consider what is the scope of my project, if I am anticipating complex system with lots and lots of various implementations, then I would go for Spring, for moderately complex system I would go for JSF.
One also need to consider if the primary designer leaves the team would other team members or a new comer will be able to pick particular MVC framework with ease or not (consider using well known MVC vs not-so-well-known-personal-favourite-picked-out-of-google). How mature the particular MVC framework is, are there good books written about it etc. These are just from top of my head.
Also keep in mind when there is too much of Spring (or any other ioC container) involved, there comes a time (after 8-12 months) when you are unable to debug code correctly because there are so many classes involved that you just keep tracking which class goes to which spring context files etc.
Finally, as one of my mentors used to say, don't solve the world problems (by using lots of design patterns), solve the problem at hand. :-)