Adam Bien's Weblog

Thursday Jul 27, 2006

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:

  1. J2EE/JEE is only EJB technology.
  2. EJBs are too complex.
  3. We have only to consider ther development phase. The maintenance and production is not important.
  4. Lean POJOs and transparent persistency is easier to understand for a beginner, than heavyweight EJBs.
  5. 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.
  6. 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.
  7. Monitoring, management, profiling are not necessary.
  8. It is very easy to implement everything you want in a web container.
  9. It is sufficient to ensure the functionality of a distributed application with unit- and integration-tests.
  10. and JEE will die. :-)
I will discuss the fallacies in detail in following entries.


[my tweets]  Rss My book: Real World Java EE - Rethinking Best Practices

Kommentare:

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 #

Senden Sie einen Kommentar:
  • HTML Syntax: Ausgeschaltet
Interviews/About
My Recent Book
Java One 2009
CommunityOne East N.Y.C
JavaONE 2008 Interview
Search
...the last 150 posts
...the last 10 comments
greenfire.dev.java.net
Links
my.netbeans.org
Visitors
License