This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Object Relational Mapping and the fly likes Entity bean failure Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Entity bean failure" Watch "Entity bean failure" New topic
Author

Entity bean failure

Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8927

I just thought of listing down points why entity beans failed. If someone disagrees or has new points please reply to the thread

1. Entity beans are complicated. They have complex lifecycle and interfaces (home ,remote, EntityBean interface)
2.Most of the datastores are RDBMS but entity bens tried to provide a generic solution.
3. There is no easy support for inheritance.
4. Difficult to test.
5. Patterns like DTO,DAO required.
6. Complicated deployment descriptor.
7. Entity beans are get/set objects with no behaviour.
8. Difficult to port.

I am sure that many here will have excllent point.Please share them here.
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: Entity bean failure
 
It's not a secret anymore!