For a non-Java developer, it might either break the myth that Java EE is too much based on XML, or reinforce it. Spring, JAX-RS, JSF etc. now allow no-XML configuration, and they are not as verbose as they used to; but still it might seem daunting for someone outside (I'm also someone from outside in this respect too, I have been doing Java EE only for the last 3 months, (I had Django/Python experience before) and it has been hard to get to learn all the Java EE technologies by myself (e.g. how many ways are there to do DI in Java EE? Spring, CDI, JSF, with or without XML etc.)
Thanks!
Java is great and you can be as productive as you want.
Another thing is that the JVM environment is getting richer every year, with more Frameworks and languages.
As I said before, Java is a work horse. My fun coding is now in Javascript and Scala, but to work, for me nothing beats Java and it's stack.
1. Maven + Eclipse/IntelliJ
2. JavaEE 6 and Spring 3.1 (note the specific version)
3. Spring Data (previously known as Hades)
4. JUnit or TestNg and Mockito.
5. Findbugs, Checkstyle, Sonar, and Hudson.
You can ignore JSF unless it is the mandate. Sticking with minimum JSP or transmiting JSON works fine regardless your stack of choice.
PS: JavaEE 6 supports dependency injection and a bit of AOP.