CDI (JSR-299) and Weld 1.0 are almost a reality. We've got word from Sun that CDI and the rest of Java EE 6 will be submitted to the JCP on November 9. I've spent the last few days filling out the Javadoc for the CDI API and SPI packages and making some last-minute cleanups to the spec. Meanwhile, Pete and the others are fixing bugs in the RI and TCK. This process has taken more than 3 years, and an incredible amount of pain, but we're now looking at one of the most well-reviewed JCP specifications ever.
Created: 29. Oct 2009, 18:09 CET (Gavin King)
Last Modified: 29. Oct 2009, 18:10 CET (Gavin King)
Gavin, where will the revisions to the spec be (and what's being fixed)?
I'll post the spec here when we do the final submission.
There's no really major changes, mainly just clarifications.
The only user-visible changes are:
Minor stuff.
Great news. We're looking forward to getting started with it over here.
Hrm, actually all 3 of those changes are fallout from the 330 alignment.
Like I said before, CDI is an unprecedented breakthrough and the JPC needed some people enabling us a more efficient, streamlined development. Thanks all for being realistic and making this (almost) a reality.
There's also a bug, I think Dan said something about, or he was going to in Section 4.3 at the end. The types are generic types are wrong.
Oh yeah, few little grammar things here and there, but nothing major.
Great news. JEE6 will be a fantastic enterprise framework. JSF2 with RichFaces, CDI and JPA2 are going to be a great team. Keep the good work up so there will be more JSR like this one.
This will be a complete and theoretically driven back end/framework. (As opposed to evolved arbitrary decisions that become a framework more about memorization than thinking.) And they said computing couldn't be fun anymore!
Kudos Gavin and loved the JUG in Boston. Hope to see ya around the circuit.
Congrats to the JBoss team. I'm hoping to use EE6 one of these days and/or Seam 3. I hope that CDI/Weld/Seam3 will perform well in large, clustered production projects. JSF1.2/Seam2.x has had performance problems in the past. I hope the new EE6 stack has properly identified and addressed these problems...
Congratulations on job very well done, you had to climb some mountains (hastily erected in front of you) on the way. I think anyone without a political agenda (and maybe even some with an agenda!) will agree you have made Java EE 6 great. Thanks Gavin, and thanks to any unsung hero's on your team.