Why they made EJB so complicated?

[lao zhang]

I almost finished first reading Head first EJB. As I was reading the book, a question was raised .Why did they make EJB so complicated? How is the productivity of developing EJB application? How can company afford hiring experienced J2EE developer or train them?
[ December 13, 2004: Message edited by: lao zhang ]

[Valentin Crettaz]

The SCBCD exam does not address this issue.

Moving this to the EJB forum. Please continue this discussion there. Thank you

[Srini Madala]

The much awaited EJB3.0 addresses these issues. It alleviates some of these complexities such as deployment descriptor is now optional. You can specify the bean type, transaction etc as annotations in the file itself. Another improvement is that there is no need to call the unused container callback methods, no home interface at all, and much improved entity design.

[Pradeep bhatt]

You could use Spring AOP framework before EJB 3.0 becomes a standard. It will take couple of years for EJB 3.0 to be used widely.

[lao zhang]

Yes. They should make thing as simple as possible, but not simpler. Coding EJB should be a pleasant job for developer, not torture.

[Stan James]

One goal was to shift work away from the developer and onto the container. Such frameworks have the highest vale if they are so simple as to be nearly invisible. A question like yours is a good way to judge how well they did. Still, quite a few of us find EJB pays off in real life projects with robust solutions to some pretty tricky problems.