EJB's 101 Damnations By Robin Sharp, Dino Fancellu Edited by Matt Stephens

24 February, 2002

This is the tale of 101 Damnations. Sadly, it's no Disney story - in fact it's more likely to have been pulled from the pages of the Brothers Grimm.

Whilst writing the EJB modules for our JGenerator product, we started punting an email back and forth containing all the issues we had with EJB. And there were many. Before we knew it we ended up with 101 howlers.

In this article we present an edited version of the email. It isn't a complete list and there may be some overlapping issues. If there is enough interest we will turn it into a more formal analysis.

Before you flame us for chasing after your sacred cow with a big stick, all three of us have belonged to the "pro-Java" lobby since Java was in its first beta, and we still do. We have evangelised Java at every company we have worked at. However, EJB just presents so much that is wrong and messed up that we felt we had to speak out.

The 101 issues are divided into the following categories:

•  Conceptual
•  Design
•  Development
•  Deployment
•  Runtime
•  Knock-on Effects

And finally there's a conclusion, containing some heartfelt suggestions for improving the EJB spec.

(Each page ends with a >> Next Category link, so they can be read in sequence).

We want Java and J2EE to succeed. We want it to remain the platform for developing server-side applications. We just hope that somebody at Sun is paying attention…

>> First category: Conceptual (High-Level Damnatians)

Message Forum
Join in the discussion. Please try to keep it constructive!

Read the entire article as an Acrobat file.

<< Back to Programming

<< Back to Software Reality