What stack would you use for a new web Java project if you started today? [closed]

Question

If you were to start a brand new Java project today with the following requirements:

• high scale (20k+ users)

• you want to use something that is fairly mature (not changing dramatically) & wont be dead technology in 3 years

• you want something very productive (no server restarts in dev, save the code and its automatically compiled and deployed), productivity and time to market are key.

• some amount of AJAX on front end

• no scripting language (JRuby, Groovy, PHP etc.), it has to be Java

• has to support i18n

What stack would you use & Why? (when I say stack, I mean, everything soup to nuts, so app server, mvc framework, bean framework, ORM framework, javascript framework, etc...)

Answer 1

I would consider using a Java EE 6 stack:

• GlassFish v3 as app server: not heavy, very productive during development (and GlassFish 3.1, to be released before the end of the year, will have Centralized Administration / Clustering and High Availability / State Replication)
• JQuery, JSF 2 (or Wicket) for the presentation
• CDI, EJB 3.1 (Lite?), JPA 2.0 (Hibernate 3.5+ or EclipseLink)
• Arquillian⁽¹⁾ with Weld SE and/or GlassFish Embedded for testing

_{(1) See also:}

• Testing Java EE the JBoss way
• Arquillian 1.0.0 Alpha2 - Released