B Day (The Big Day) JDO2 voted
JDO2 passed the second round of the JCP (Java Community Process) Board of JAV (Java Community Process), which became a formal JCP standard without opposition. Let us remember that in the first round of voting a month ago, JDO2 failed to pass in up to 10 opposition tickets. How is this dramatic change happened?
First, let's take a look at the technical political corner of Java community. The complexity of EJB2 makes it sick and unavailable by Java users and developing communities. With the emergence of JDO, EJB manufacturers have seen threats and are facing selection. The POJO model that is not relying on the container is used by the JDO standard to achieve mapping and data lasting comparison of EJB2 is far more than the development of EJB2. This technique exceeds the EJB manufacturer in a very embarrassing situation.
All along, EJB2 is a standard data persistence layer in the J2EE architecture. EJB vendors rely on EJB's dependence on containers to make users with high profits on an expensive EJB server (Application Server). If EJB technology
Beyond and give up, the impact of the current EJB vendor is huge. Can EJB manufacturers accept and turn to JDO standards? Unfortunately, it is not feasible. The reasons are of course not technical. If you turn to JDO, it means that EJB manufacturers need to recognize their technical disadvantages and share an enterprise-level data persistent layer market with emerging JDO vendors. This is obvious that the EJB manufacturer is happy. Upgrading EJB and maintaining EJB's corporate data persistent layer standard is the only way to go.
But how to upgrade EJB? The object relationship mapping and long-lasting PLAIN OLD JAVA Object (POJO) model has become a consensus of the Java industry, and EJB can only develop in JDO, and the JDO manufacturer with rich POJO model and a complete API, EJB Manufacturers have clearly lack this knowledge and experience accumulation in this area. This time hibernate is selected. The Hibernate Authors and JDO Standards Expert Groups are unpleasant, mainly consisting of EJB experts from EJB manufacturers to absorb the Hibernate authors and make Hibernate as the implementation basis for the EJB3. This is a huge opportunity for JBoss / Hibernate, making JBoss to become the leader of EJB3 standard from the EJB manufacturer, and also pushed JBoss / IhihiHibernate to the front line of JDO development community. However, JBoss / Hibernate has a negative effect on JDO2's untrusted speech on the battle and propaganda, but also has a negative effect on JBoss / Hibernate.
The original EJB giants maintain low-key and silence, secretly applied to the Sun and JDO expert group, hoping to achieve the merger of EJB3 to JDO2, avoiding the competition of future business data lasting markets. In the case of all parties, J204 JDO expert group and EJB3 expert group jointly signed a public letter, promised to share each other, jointly develop new Java general data persistent layer standards, while 6 JDO expert group members were Absorbed into the EJB3 Expert Group to develop EJB3 and new Java general data persistent layer standards.
The data persistence model of JDO2 and EJB3 is similar, and the function is also made, the main difference is the syntax and default query syntax of object / relationship mapping. However, JDO2 is already a mature API, and more than 30 manufacturers support this standard and considerable user group, and EJB3 is still in the draft stage. The maturity and time of technology are advanced to EJB3 in JDO2.
Comprehensive these background factors, JDO2 was held in the first round of voting (mainly EJB vendors in the JCP Executive Committee), which is both unexpected, also unexpected. It is an expectation that EJB vendors obviously do not like JDO standards that have already formed a monopoly EJB market. It is expected that EJB manufacturers in the Executive Committee seem to forget the obligations and responsibilities as members of the JCP Executive Committee. (10 votes against no tickets based on technical reasons), to block a competitive candidate standard for your own market interests. If this incident occurs 5 years ago, it is accustomed to developing communities and users who are going through the manufacturers and users. However, in the development of the community, the developers and users have recognized that the so-called standards should not be developed by the manufacturer for their own development and interests, but the needs of developers and users.
JDO has existed and developed for 2 years. Although JDO's development community is small compared to open source, the accumulation of business users, especially high-end users, especially in banks, telecommunications, governments, etc. And supported projects, JDO vendors have got a considerable market. When the JDO2 first round of voting was released, the JCP Committee's email fantasy flooded, and criticized the JCP Executive Committee for the political votes made by private interests. The JDO users of the red workplace also responded to calls, issued an appeal message. Many of these emails have also been sent to the JDO expert group (some users don't know the difference between the JCP Executive Committee and the JDO expert group), the author is fortunate to see a few, and the words cannot be said not intense.
Under the pressure of developing communities, especially users (many JDO high-end users are often used by users of EJB servers), JDO2 in the second round of voting is passed under the coordination of JDO support vendors / organizations in Sun, Apache. .
This is a very happy result. More importantly, it is the first development community and users in the history of JCP and users to fully participate in the standard development process, and make their own voice, maintain development communities and users at the critical time. Your own interests. This precedent will also encourage more manufacturers, users and developers to join JCP, actively participate in standard development, and promote the fair competition and prosperity of Java communities.
