I read Pojos in Action book.
It says EJB has major 2 disadvantages.
1)cumbersome nature of the development processwhen using EJBs doesn’t allow developers to take advantage of many of the best
practices used for “normal” Java development
2)EJBs encourage developers to write procedural-style applications
1)cumbersome nature of the development processwhen using EJBs doesn’t allow developers to take advantage of many of the best
practices used for “normal” Java development
Which version of EJBs does that book talk about? EJB3 (and EJB3.1) are no longer cumbersome.
Samanthi perera wrote:
2)EJBs encourage developers to write procedural-style applications
I haven't read that book so I don't know in what context this is stated. And I also don't see how that applies to EJBs.
Personally, in the case of EJB 3, I would disagree with both of those statements. I think that EJBs are good OO - especially as they can increase decoupling - and are not at all cumbersome to write.
Ran Pleasant
Ranch Hand
Joined: Jan 16, 2003
Posts: 75
posted
0
Samanthi perera wrote:EJBs encourage developers to write procedural-style applications.
I strongly disagree with this. I am currently having to deal with a number of co-workers who do write procedural code in EJBs. The root of the problem is not with EJBs themselves, rather it is rooted in a lack of knowledge about EJBs, OOAD, UML, basic Object Oriented Theory, and the use of an Anemic Domain Model. People who don't know EJBs but do have good OO skills, understand the theory behind OO, who do OOAD, etc., will not go into their first EJB and start writing procedural code. Why? Because they are object-oriented programmers!
0
