Since you have a close working knowledge of the EJB 2.0 spec for writing your book and it sample code, and maybe you also have a grasp of EJB 3.0, my question is:
What other features/enhancements, that reach beyond today's EJB 3.0 spec, do you think would be necessary to really make EJB technology the most widespread, high performance, business component object model of choice in the java world ?? [ July 26, 2005: Message edited by: chris coleman ]
Sun Certified Java Programmer for the Java2(tm) Platform<br />IBM Certified Solution Developer, WebSphere 3.5
In addition to above issue, what technologies/framework, e.g. Spring, Tapestry, etc, can be "integrated" with EJB 3.0 specification or further enhancements? As you know, now EJB 3.0 has borrowed the idea from Hibernate.
Chris and Nick: The most robust system we have around is the universe we live in, and it works in the simplest possible way. In other words, the laws of nature are in their simplest possible form (note that simple does not always mean easy) and almost all scientists will agree with me on that. To that end, I'm excited about EJB 3.0 because its main purpos is to "improve the EJB architecture by reducing its complexity from the developer's point of view" and I assume that by "reducing complexity" they mean simplifying :-). "Simpliication" in software often means automation, abstraction, and standardization. But we pay for all the advantages of "simplification" in losing flexibility, and optimizations for specific environments. So it's very tricky to strike a balance. As much I'm excited about EJB 3.0, there is quite a bit of "simplification" in there. It's always a good idea to maintain a healthy skepticism to see how it's going to play out. Then, there are some side questions: who'll be running the Java show three years from now? What other technologies may emerge by then? So right now, instead of wishing for more "simplification", I would rather like to sit down with the Spring folks to see if we could vision some kind of unification here :-).