I have strong hopes that pressure from some of the IoC/Lightweight container advocates, as well as the Hibernate types, is registering with the vendors on the JDO and EJB3 JCP bodies. I'd much rather be able to advocate a complete and workable standard than endure endless religious battles in-house about who'se framework is better. If J2EE can just do something REASONABLE with persistance, we all benefit, and the standard can advance.
I don't buy that dependency injection versus JNDI means all that much to your typical developer, it's way too much 'inside baseball'. I do think it's a huge hole that you essentially have to ignore big parts of J2EE (thru crummy CMP persistance) and do something non-standard...
A lot of dissing of J2EE at the end boils down to CMP. If that was not an issue I don't think IoC would be getting that much attention. That's not to say those interesting ideas, AOP approaches, etc. don't have a place in the standard, it has to grow and evolve. An industry standard with wide vendor support and a healthy open-source community keeping it honest is what we need.
I think, tho, that I want to take 'pragmatic' back...With a workable CMP and JDO implementation (work that out guys!), and backing by the vendors, you won't worry about eating the elephant, I'm afraid that the elephant might eat you!
Cheers,
MC |
java.net RSS Feeds
