Java EE 6 is now released. In Sun's official website, there are a series of articles on Java EE 6 of the technical standards described in detail. 51CTO development channel on this series for the translation, bring you a first taste of the new features of Java EE 6. This series of articles will be updated every Tuesday, today introduced the main objectives of Java EE 6.
Java Platform Enterprise Edition (Java EE) is to build Java enterprise applications industry standard, which to a solid Java Platform Standard Edition (Java SE), based on adding support for scalability, accessibility, security, integrity and other enterprise applications, database and system services needed.
Since the first release since 1999, Java EE has developed into a feature-rich, high-performance platform, the latest version of the Java EE 6 with an emphasis on simplicity and ease of use. In fact, the use of the platform, the current version of Java EE 5 Development of Java enterprise applications has never been easy.
Java EE 6 in the previous version based On made a lot of progress, add a Daliang of new technology, Qi Zhong some inspiration from the dynamic Java EE technology community, it further simplifies the platform, compared with the previous version of Java EE expanded availability.
In this paper, the goal of Java EE 6. The following is a Java EE 6 platform, the main objectives:
Over time, Java EE platform has become more and more bloated, in order to solve this problem, Java EE 6 introduces the concept of Profiles, Profiles include classes designed for specific applications, Java EE platform configuration. Profiles may include a Java EE platform technologies, and has passed the Java Community Process (JCP) of a subset of additional technology, these additional techniques are not part of Java EE platform. Java EE 6 was first introduced these Profiles: Web Profile, designed for Web application development, a subset of Java EE platform, Web Profile includes only those most Web application developers need the technology, not including those developers do not usually needs of enterprise-class technologies.
In addition, Java EE 6 platform has identified a number of candidate technologies, which candidate technologies, including new technology has been replaced by technology, or technologies that are not widely promoted, the candidate will become the platform technology means that the optional components, not the necessary components.
Scalability and better
Over time, new technology has become a Web or enterprise application developers are increasingly interested in the object, Java EE 6, including better scalability, compared to the previous version of the service provider with more interfaces, so you can use the standard method in your implementation into Java EE 6 technologies, or even frame. Once inserted, these technologies and built on Java EE 6 platform, the tools as easy to use.
Focus on scalability, Web tier, Web application developers often use third-party framework, but allowed to register these frameworks can be used in Java EE Web applications may be very complex, usually require developers to add or edit complex XML deployment descriptor file, Java EE 6 through self-registration, you can use these frameworks, it is easy to merge and configure them in the application system.
Further simplifies the development model
Java EE 5 has given way to Web and enterprise application development has become very convenient, for example, Java EE 5 introduces a more simple Java objects based on common (Plain Old Java Objects, POJO) and Enterprise Application Notes programming model, and abolished on the need for XML deployment descriptors. In addition, Enterprise JavaBeans (EJB) technology has also been streamlined and require fewer classes and interfaces, through the use of Java Persistence API (Java Persistence API, JPA) provides the advantages of a simpler object-relational mapping.
Java EE 6 to enterprise or Web application development easier, and the platform in many aspects of usability improvements, for example, you can use the annotation definition of Web components, such as Servlet and Servlet filters. In addition, the dependency injection annotations have been standardized so that cross-class framework into a more portable. Other Java EE application packaging requirements are also simplified, for example, you can add directly to a WAR file enterprise Bean, no longer need to encapsulate the enterprise Bean JAR file, and then packaged into JAR files in the EAR file.