JEE 6 is a huge leap forward compared to how J2EE used to be. However, there are a few problems. First of all, JSF is the most horrible framework for creating

JEE 6 is a huge leap forward compared to how J2EE used to be. However, there are a few problems. First of all, JSF is the most horrible framework for creating web applications that I've ever used. Its intention is to make web development easier, but what you get is a huge mess of HTML and JavaScript that introduces a lot of new problems. Escpecially since it gives you the impression that you don't need to know HTML and JavaScript to work with it. EJBs are a lot easier, and as long as you don't access them remotely, you don't need interfaces or XML files. If you put them remotely, you need both. With injection you don't need to look up EJBs manually, except if you put them remotely - because if the reference to the remote EJB is invalidated (i.e. if it's accessed while the remote server is down), you'll need to look it up manually again. As long as you choose something other than JSF, JEE 6 is fine. Of course, then there's the application servers. I've only tried Glassfish (for a while it was the only fully certified JEE 6 app server), but it had a few problems - I heard one of the latest versions had a GZip filter that would have spinning threads taking 100% CPU. JEE has come a long way, but I'll probably choose Spring for my next Java project.