Java Enterprise Edition (EE)
Oracle has long been a big time Java proponent and one of the largest JCP members. The company was involved with the Java EE specification when it was created over a decade ago. Therefore, it should be no surprise that Oracle has become a big player in the Java middleware space.
Through development efforts and acquisitions, Oracle has assembled the Oracle Fusion platform, which consists of a full Java EE stack, SOA-based services, an ESB, transaction server, development tools, and much more. With the acquisition of Sun, Oracle now owns the Glassfish software suite, which is also the Java EE reference implementation. They made it clear that Glassfish will stay mainly as the reference implementation, listing it for business use only in tactical applications. Exactly what Oracle means by tactical isn't clear, but I would assume it will be allowed for use with existing customers, and possibly for embedded use. Given previous statements about focusing on Java SE embedded solutions, this is probably a safe assumption. Oracle's WebLogic application server will remain the strategic component in the Fusion stack.
As for the reference implementation and the future of Java EE, Oracle stated they would put effort into the following areas:
Modularity and Open Standards. Java EE 6 implies a more modular Java EE implementation through the definition of profiles. This is to allow vendors to create smaller subsets of their entire Java EE stack for specific uses, addressing the issues of cost and complexity associated with using Java EE. Increasing the modularity, and defining standards to do so in the process, helps to simplify Java EE even further, and allows it to be used in situations it may not be best suited for today.
Currently Java EE 6 specifies two profiles: the web profile (Servlets, JSP, and JSF only), and the Java EE enterprise profile (the entire stack). Obviously there's room in between for more standard profile definitions. For instance, a telecommunications server profile with support for Session Initiation Protocol (SIP) is one suggestion.
Beyond profiles, modularization can be used to deploy middleware into devices other then servers. For instance, embedding part of the Java EE stack into mobile devices such as security cameras, RFID readers, or any other "smart" device you can think of, opens the door to a standard Java programming model that can be deployed in a wide range of uses.
Although Oracle hasn't outlined its specific plans in this area, I predict that a solution where JavaFX is integrated with Java EE in the future will be proposed to address the issues around Ajax. In fact, based on statements made by Larry Ellison at JavaOne in 2009 regarding Ajax and JavaFX, this sounds like a safe assumption.