当然，每个人都会有所不同，但我建议使用Spring MVC，因为它是基于请求的框架，如Struts 。当然，你会想要了解像控制/依赖注入反转这样的核心Spring的东西（但我会考虑加分......）以及你将用于数据库访问的任何东西（只是JDBC？Hibernate？ iBatis？等。）

Of course, it's going to be different for everyone, but I'd suggest Spring MVC, as it's a request-based framework like Struts. Of course, you'll want to learn about core Spring stuff like Inversion of Control / Dependency Injection (but I'd consider that a plus...) and whatever you're going to use for database access (just JDBC? Hibernate? iBatis? etc.).

JSF是基于组件的，这与基于请求的框架有点不同。如果你打算去JSF路线，我建议你看看JBoss的Seam。它更像是一个前端框架，它使用JSF作为Web /表示端，EJB作为后端。几乎所有使用它的人声称它使JSF和EJB比它们本身更有用。

JSF is component-based, which is a bit different paradigm from request-based frameworks. If you do plan to go the JSF route, I'd suggest looking at Seam from JBoss. It's more of a front-to-back framework that uses JSF as the web/presentation end and EJB as the backend. And pretty much all the people who've used it claim it makes JSF and EJB more usable than they are by themselves.

祝你选择哪种技术好运。 （听起来你需要它 - 严格的时间表和一个规定网络框架的客户？）

Good luck on whichever technology you choose, though. (Sounds like you'll need it - strict timelines and a client that's prescribing web frameworks?)