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.


NEW: Online Workhop Effective WebApps without Frameworks is also coming to: MUC Airport.

Airport MUC workshops: Web (SPA, PWAs, Offline, Desktop, Mobile) Applications Essentials and Effective Web Applications. No migrations. #usetheplatform

Podcast: airhacks.fm and newsletter: airhacks.news

A book about rethinking Java EE Patterns

Comments:

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 ...

Posted by Stefan Tilkov on October 18, 2006 at 11:55 AM CEST #

FALLACY 1: http://www.adam-bien.com/roller/abien/entry/fallacy_1_j2ee_java_ee
FALLACY 2: http://www.adam-bien.com/roller/abien/entry/fallacy_2_ejbs_are_too
FALLACY 2.5: http://www.adam-bien.com/roller/abien/entry/fallacy_2_5_concurrency_persistence
FALLACY 3: http://www.adam-bien.com/roller/abien/entry/java_ee_fallacy_3_we
FALLACY 4: http://www.adam-bien.com/roller/abien/entry/java_ee_5_fallacy_4
FALLACY 5: http://www.adam-bien.com/roller/abien/entry/fallacy_5_jms_jca_jta
FALLACY 6: no fallacy 6 article, but: http://www.adam-bien.com/roller/abien/entry/ror_persistency_vs_jpa_java
FALLACY 7: http://www.adam-bien.com/roller/abien/entry/fallacy_7_monitoring_management_profiling
FALLACY 8: http://www.adam-bien.com/roller/abien/entry/fallacy_8_it_is_very
FALLACY 9: http://www.adam-bien.com/roller/abien/entry/fallacy_9_it_is_sufficient
FALLACY 10: http://www.adam-bien.com/roller/abien/entry/fallacy_10_and_javaee_will

Posted by Danilo Piazzalunga on October 13, 2011 at 12:37 AM CEST #

@Danilo,

thank you very much! I would call that: crowd sourcing :-)

Enjoy Java EE !,

adam

Posted by Adam Bien on October 13, 2011 at 01:36 AM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
Online Workshops
realworldpatterns.com
...the last 150 posts
...the last 10 comments
License