Normalization of JSR 299 and possible arrival of JSR 330

Normalization of JSR 299 and possible arrival of JSR 330

Reprinted by the author:

By: 88250
Blog: http:/blog.csdn.net/dl88250

MSN & Gmail & QQ: DL88250@gmail.com

 

Currently, JSR 299 (contexts and dependency injection for Java ee) is in the Community review status.
It is expected to appear in the Java EE 6 specification in September this year. JSR 330 (dependency injection for Java
) Is a submission specification. No standard file can be downloaded.

299 of lead is Gavin King (hibernate/seam lead) from JBoss/RedHat, and 330 of lead is Bob Lee (guice lead) from Google and spring. Both of them are technical personnel and private friends.

However, we can see from the canonical name that the conflicts... are di, which makes the Java Community confused. Do we need two sets of di standards?

Gavin's blog post in May 7
He said his views, and one stone stirred up a thousand waves... two leads made technical judgments on each other: Gavin is a typical Java EE supporter, while Bob Lee is the defender of Java SE.

In a series of replies, Gavin did not change its original nature, but expressed great dissatisfaction with the proposal of 330. In this regard, the regulations were redundant and 299 of the functions involved were covered, and do better. I also laughed at the fact that Bob submitted some javadocs specifications ....

Bob made some answers and said that Gavin did not understand the 330 standard .... however, Bob is indeed the defender of Se. He talked about various kinds of ejbs and questioned EJB Lite in the coming Java EE 6. However, Bob's support for JSR 294 (improved modularity in the javatm
Programming Language) is confident

On July 6, May 19, Gavin re-released a 299 community review version.
Change the canonical name to for javaee. It seems that we are still firm in the EE line and hold on to Bob's Norm: "I am my, you are yours, and you are walking.

The Java camp has always been so turbulent. It is neither a standard implementation nor a standard implementation. For developers, it is easy to lose themselves if they follow them blindly. Therefore, I suggest you use your own set of IOC/di, 299/330 holding a wait-and-see attitude