It's good to see some critical feedback on the JEE spec. I'm glad I'm not the only one questioning some of the merits of the JSRs. I'm also disappointed that the blog-o-sphere picked up on Apache's "the JCK is not really open" complaints, but seem to have completely missed (or don't have a response to) SpringSource's "too much, in the wrong places" complaint.
Granted, Seam looks to be very interesting. The biggest killer (IMHO) is JSF. Now, if the new JSF spec fixes that... perhaps it could be viable. The question remains, are Spring's complaints of "too much risk" valid? (Seam appears to be a pretty good working prototype of this JSR). Yes it would be nice to have way to easily piece together simple data driven web-apps. I personally believe JEE is still overkill for this.
Regardless, I think it is most important that the entire Java stack makes it easy to "compose" software. The easier it is to "compose" the more it encourages people to write modular code. I don't think dependency injection => modular code, but it sure encouraged *some* folks to start writing better code.
Although spring is a *rather large* codebase, it still feels to be one of the better designed library stacks for the Enterprise Development. I often find classes inside it highly useful. More so than the JEE spec. Possibly it's because they took a closure-like approach to their apis. Hmmm..... closures + java? what a novel idea.