Matt Raible takes on the argument that the age of Java Frameworks is over. One interesting aspect of the Java ecosystem is that there’s always some new thing out there that we’re supposed to be migrating to. And they’re nearly all just terrible in terms of productivity. Now apparently, we’re supposed to be looking at Java EE 6. I don’t even know what that is, but I’m sure it’s awful. In the meantime, I continue to plug along with Spring and Hibernate, using them in the simplest way I can.
Here’s a snippet from a post on migrating from Spring to Java EE:
Does it all make sense now? Do you know how to solve every problem? Probably not, but when it comes right down to it, using Java EE can be even simpler than using Spring, and take much less time. You just have to find the right guides and the right documentation (which is admittedly a severe sore-spot of Java EE; the documentation is still a work in progress, but is getting much better, save blogs like this one.) You have to turn to a vendor like JBoss, or IBM in order to get the use-case driven documentation you need, and they do have documentation, it’s just a matter of finding it.
Where do I sign up?