Adam Bien's Weblog
Common J2EE/Java EE Fallacies
At the beginning of almost every project, there is an intense (almost religious) discussion about using or not using J2EE. Almost every time I'm faced with the following fallacies:
- J2EE/JEE is only EJB technology.
- EJBs are too complex.
- We have only to consider ther development phase. The maintenance and production is not important.
- Lean POJOs and transparent persistency is easier to understand for a beginner, than heavyweight EJBs.
- JMS, JCA, JTA, JNDI, XA are too complex, too heavy and aren't needed at all. A lean inversion of control container could replace all this technologies.
- CMP 2.0/CMP 3.0 persistence is too complex, it is much easier to implement the persistence with a simple dataset framework or just using JDBC.
- Monitoring, management, profiling are not necessary.
- It is very easy to implement everything you want in a web container.
- It is sufficient to ensure the functionality of a distributed application with unit- and integration-tests.
- and JEE will die. :-)
Posted at 10:23AM Jul 27, 2006 by Adam Bien in Java / JEE / Architecture | Kommentare[1]
[my tweets]
Rss My book: Real World Java EE - Rethinking Best Practices


Would you mind linking to the individual entries here? I'd like to feature a single link to the series in my next JavaSPEKTRUM column ...
Gesendet von Stefan Tilkov am October 18, 2006 at 09:55 AM CEST #