JSF 2.0
Though On display at the framework layer of very intense competition, but the JSF is still stick to their territories. Although there is a lot of JSF's about ease of use and robustness of质疑声, but for the positive JSF2.0 solve these problems and put forward, it's easy to use, innovative and scalable features include:
JSF formally Facelets as view technology. Maybe you are not familiar with Facelets, it is also a tacit understanding with the combination of open source JSF view technology. Therefore, JSP and Facelets are more different from the JSF component model fit as well as the concept of the life cycle. Of course, perhaps the most powerful characteristics of Facelets is used mark-up to replace the java code to create custom components. Create custom components may be the complexity of JSF developers are complaining about most of the places.
JSF2.0 through the use of tags for EE 5 provides annotation-driven configuration based on the characteristics (for example, can use the @ ManagedBean and @ ManagedProperty). This also means that can be reduced to some extent on the faces-config.xml file size, but as nodes in the navigation of these configuration files in XML or less should not.
AJAX and JSF2.0 order to adapt to changes in the life cycle of their own, required only by the AJAX partial page treatment case. This feature makes the combination of JSF + AJAX more natural.
JSF2.0 are excellent resources for built-in processor. Of images, JavaScript files, and Outstanding performance style and so on. It can be the name of the logical resources, such as division as well as the way to a better version of the reference resources.
In addition to the above characteristics, JSF2.0 Convenience also includes many other changes. For example, to support the case to support the development of RAILS_ENV style (ie, ROR), support for the standard components are set to expand. You can take a look at the link below to open the draft JSF2.0: ? id = 314
EJB 3.1
EJB in the Java EE 5 has experienced a very large changes. May be seemingly impossible, but in fact or in the community EJB3.0 widely recognized and adopted by its people is also growing. All this may be because we need to think over how to simplify Java EE 5 how to achieve such a score. For example, JBoss Seam on GlassFish interest and enthusiasm are the key factors important. EJB3.1 is the goal of increasing business components, EJB continue to become as simple as possible. EJB3.1 following characteristics of a highly condensed summary:
Even necessary to achieve the original business interface Session Beans become optional, and is no longer forced to realize the requirements. In the use of Session Beans + JSF + WebBeans particularly useful for the next scene.
Singleton Beans increased EJB3.1 concept. Since people are more inclined to share the management of status applications, are required to ensure full thread Model. In addition, EJB3.1 new declarative concurrency control is also more flexible.
EJB3.1 a remarkable characteristic is the strong support for cron-style scheduling. In addition to the existing scheduler based on the timer timer API, the Declaration and Program of cron-style scheduling API joined.
Another strong characteristic of the @ Asynchronous can be marked by using the Session Bean to the asynchronous method call. You can even control through its asynchronous EJB method in order to return an object java.util.concurrent.Future.
EJB3.1 Lite gradual introduction of the concept of the formation of a subset of the EJB API and the application in Web Profile. EJB Lite contains only as transaction processing and Such features, and those mechanisms message, remote call, as well as scheduling and other non-essential nature of which there is no need to add. In addition to the above mentioned characteristics of the list, the
EJB3.1 features include: include EJB packaged directly into a war file can be run in embedded container Java SE environment-friendly JUnit , The use of uniform standardized global JNDI naming. EJB3.1 draft public access from the link below: ? id = 318
JPA 2.0
Java EE 6 the time, JPA has been completely isolated from the EJB, and form their own system (EJB3.0 separate JPA has been). JPA's success is no question about it. Is widely adopted by the community and the support of first-class supplier. Originally EJB2 .* We are worried that the collapse of the Enity Beans may not be able to lead once again to allow Java EE standard persistence layer, a critical success factor is the JBoss community Gaving King and unequivocal support. JPA2.0 the goal is to build on the success of the efforts to fill more gaps in the many new innovations:
JPA2.0 must add a great deal to enhance the ORM mapping features, including: support @ ElementCollection through the use of tagging to enhance the collections, maps and lists (this is not referring to relationships between entities) set to support the map of one-way one-to - many association (JPA1.0 only allows two-way one-to-many association).
EntityManager and Query API have been improved. For example, can now be obtained directly from the results of focus on the first record (JPA1.0 permit only result from a unique anti-back to a single record), specify the maximum query result set to visit the bottom of each supplier or entity manager object query, Finally is to add a pessimistic lock (JPA1.0 only supports optimistic locking).
SQL also provides JPQL similar to the CASE, NULLIF, COALESCE function, etc..
JPA2.0 the majority of developers should be to increase the Criteria API. If you Hibernate or TopLink are not familiar with the Criteria API, you can imagine it is a Java-centric object-oriented, thread-safe and can be zoned on JPQL equate a set of API. This set of API suitable for the preparation of complex dynamic query, but also to avoid analytical statement JPQL when dished out by the run-time anomaly.
JAP2.0 more complete features include: standard of secondary cache, the standard JDBC properties, the specified timeout and so on. You can at any time by following the JSR site JPA2.0 publicly about the draft to see more details: ? id = 317
Though On display at the framework layer of very intense competition, but the JSF is still stick to their territories. Although there is a lot of JSF's about ease of use and robustness of质疑声, but for the positive JSF2.0 solve these problems and put forward, it's easy to use, innovative and scalable features include:
JSF formally Facelets as view technology. Maybe you are not familiar with Facelets, it is also a tacit understanding with the combination of open source JSF view technology. Therefore, JSP and Facelets are more different from the JSF component model fit as well as the concept of the life cycle. Of course, perhaps the most powerful characteristics of Facelets is used mark-up to replace the java code to create custom components. Create custom components may be the complexity of JSF developers are complaining about most of the places.
JSF2.0 through the use of tags for EE 5 provides annotation-driven configuration based on the characteristics (for example, can use the @ ManagedBean and @ ManagedProperty). This also means that can be reduced to some extent on the faces-config.xml file size, but as nodes in the navigation of these configuration files in XML or less should not.
AJAX and JSF2.0 order to adapt to changes in the life cycle of their own, required only by the AJAX partial page treatment case. This feature makes the combination of JSF + AJAX more natural.
JSF2.0 are excellent resources for built-in processor. Of images, JavaScript files, and Outstanding performance style and so on. It can be the name of the logical resources, such as division as well as the way to a better version of the reference resources.
In addition to the above characteristics, JSF2.0 Convenience also includes many other changes. For example, to support the case to support the development of RAILS_ENV style (ie, ROR), support for the standard components are set to expand. You can take a look at the link below to open the draft JSF2.0: ? id = 314
EJB 3.1
EJB in the Java EE 5 has experienced a very large changes. May be seemingly impossible, but in fact or in the community EJB3.0 widely recognized and adopted by its people is also growing. All this may be because we need to think over how to simplify Java EE 5 how to achieve such a score. For example, JBoss Seam on GlassFish interest and enthusiasm are the key factors important. EJB3.1 is the goal of increasing business components, EJB continue to become as simple as possible. EJB3.1 following characteristics of a highly condensed summary:
Even necessary to achieve the original business interface Session Beans become optional, and is no longer forced to realize the requirements. In the use of Session Beans + JSF + WebBeans particularly useful for the next scene.
Singleton Beans increased EJB3.1 concept. Since people are more inclined to share the management of status applications, are required to ensure full thread Model. In addition, EJB3.1 new declarative concurrency control is also more flexible.
EJB3.1 a remarkable characteristic is the strong support for cron-style scheduling. In addition to the existing scheduler based on the timer timer API, the Declaration and Program of cron-style scheduling API joined.
Another strong characteristic of the @ Asynchronous can be marked by using the Session Bean to the asynchronous method call. You can even control through its asynchronous EJB method in order to return an object java.util.concurrent.Future.
EJB3.1 Lite gradual introduction of the concept of the formation of a subset of the EJB API and the application in Web Profile. EJB Lite contains only as transaction processing and Such features, and those mechanisms message, remote call, as well as scheduling and other non-essential nature of which there is no need to add. In addition to the above mentioned characteristics of the list, the
EJB3.1 features include: include EJB packaged directly into a war file can be run in embedded container Java SE environment-friendly JUnit , The use of uniform standardized global JNDI naming. EJB3.1 draft public access from the link below: ? id = 318
JPA 2.0
Java EE 6 the time, JPA has been completely isolated from the EJB, and form their own system (EJB3.0 separate JPA has been). JPA's success is no question about it. Is widely adopted by the community and the support of first-class supplier. Originally EJB2 .* We are worried that the collapse of the Enity Beans may not be able to lead once again to allow Java EE standard persistence layer, a critical success factor is the JBoss community Gaving King and unequivocal support. JPA2.0 the goal is to build on the success of the efforts to fill more gaps in the many new innovations:
JPA2.0 must add a great deal to enhance the ORM mapping features, including: support @ ElementCollection through the use of tagging to enhance the collections, maps and lists (this is not referring to relationships between entities) set to support the map of one-way one-to - many association (JPA1.0 only allows two-way one-to-many association).
EntityManager and Query API have been improved. For example, can now be obtained directly from the results of focus on the first record (JPA1.0 permit only result from a unique anti-back to a single record), specify the maximum query result set to visit the bottom of each supplier or entity manager object query, Finally is to add a pessimistic lock (JPA1.0 only supports optimistic locking).
SQL also provides JPQL similar to the CASE, NULLIF, COALESCE function, etc..
JPA2.0 the majority of developers should be to increase the Criteria API. If you Hibernate or TopLink are not familiar with the Criteria API, you can imagine it is a Java-centric object-oriented, thread-safe and can be zoned on JPQL equate a set of API. This set of API suitable for the preparation of complex dynamic query, but also to avoid analytical statement JPQL when dished out by the run-time anomaly.
JAP2.0 more complete features include: standard of secondary cache, the standard JDBC properties, the specified timeout and so on. You can at any time by following the JSR site JPA2.0 publicly about the draft to see more details: ? id = 317