Java ee 5 specification was born

When I return from the May Day holiday, I am used to visiting the news at http://www.theserverside.com/. the Java ee 5 specification was officially released in May 1 (Java ee 5 passes-ready, set, code !). As a result, I was deeply touched by the hard work of overseas workers who were willing to give up enjoying their own festivals to encourage the early birth of the Java ee 5 specification, no words.

This news immediately attracted a large number of javaer comments on theserverside, and it was a bit rewarding if I flipped through it. However, I am not very touched by the emergence of Java ee 5 specifications. Today, when the open-source community is booming, especially when EJB becomes the target of the public, the private power seems to completely replace the official authority. Without the Java ee 5 specification, we have also lived a lightweight life by using the "large container" combined by multiple open-source frameworks. Without the Java ee 5 specification, we use the "old" technology. Although there are not many new features of cool, we are still comfortable.

Let's take a look at how the official website locates Java ee 5:

The focus of Java ee 5 is of development. to simplify the development process for programmers just starting with Java EE, or developing small to medium applications, we 've made extensive use of Java language annotations that were introduced by j2se 5.0. annotations reduce or eliminate the need to deal with Java EE deployment descriptors in parallel cases. even large applications can benefit from the simplifications provided by annotations.
One of the major uses of annotations is to specify injection of resources and other Dependencies into Java EE components. injection augments the existing JNDI lookup capability to provide a new simplified model for applications to gain access to the resources needed from the operational environment. injection also works with deployment descriptors to allow the deployer to customize or override resource settings specified in the application's source code.

It can be seen that the blueprint described in the Java ee 5 specification is very beautiful, which seems to be inspired by Ror, the "Idol School", which takes reducing development complexity as the first place. From the specifications, we can see that it has learned a lot from the open-source community and integrated it into itself. This is a pleasant phenomenon. This may make it a success, but the official pace seems to be always slower than "fashion", and it was just born, still lack of support from vendors and open-source communities. In this ever-changing world, what is the future of the Java ee 5 specification?

We will wait and see.