The goal of this blog post is to walk you through an Java EE 6 application from a simple, static
web page until we have a full blown stack that consist of the stuff in the list below. I'm calling this
stack Summer because after a long, hard winter Spring may be nice but boy, wait until Summer kicks in ;-)
Recently, we've been working hard on a solution to improve the testability of Java EE, and particularly JBoss AS. I'm pleased to say that a critical piece of puzzle, Arqullian, is now available. Congratulations to Aslak and the Arquillian team for releasing the first alpha of Arquillian! You can read more about Arquillian's mission, and our plans for Java EE testing below; alternatively, there are some quick links at the bottom if you want to dive right in.
I'm excited to announce that plans for a top-level JSR for the Unified EL are underway. It's likely that Kin-man Chung will be filing a JSR in the near future. But we aren't waiting to get the discussion started. Kin-man has started the open el-next mailinglist (firstname.lastname@example.org), where we will begin itemizing priorities and designing features. We'll then convert the requests into issue reports as they are solidified.
With the release of Java EE 6, I've seen a number of recurring, but rather curious, arguments against upgrading to the new platform. These are usually deployed by folks who are using a homegrown stack consisting of a servlet engine like Tomcat or Jetty together with a number of open source frameworks like Hibernate and Spring.