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.
Hello Alex, did you use EntityBean in your part 2? I am thinking of using some ORM such as hibernate instead? what's your thought? is EntityBean required? Good luck on your test. Thanks. B
Joined: Sep 24, 2006
Yes, I followed the classic J2EE framework where entity beans (CMP) are used to represent the domain objects and session beans are as facades in the EJB tier. Moreover, I mentioned in the assignement that entity beans were applied for mapping single entity only. For those scenarios where large quantities data with complex relationships are retrieved, I used the Fast Lane Reader pattern (i.e. DAO component) because of the heavy-weight lifecycle management imposed in EJB spec.
There is no right or wrong on using EJB or Hibernate. Your assignment will be marked base on how you jusify your solution. For example, performance, scalability, mantainibility or even productivity (time to market etc)..
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