Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Cade's example doesn't specify EJBs ??

 
H. Hafer
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dudes,

the class diagram of the example in Cade's book does specify <<StatelessSessionBean>> (e.g. for the OrderProcessor class), however it does not specify any <<EntityBean>> where I would expect it (e.g. for the Customer class). Why? Is any class not stereotyped taken as entity bean? While we are at it, why is class ShoppingCart not stereotyped as <<StatefulSessionBean>>?

Would Cade's style be appropriate for the assignment?

Did I miss the point?

Thanks for help,
Harbo
 
Tomi Tuomainen
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Harbo,

In Cade's system data is persisted into legacy systems and entity beans won't help much there. Although it seems that you could use an entity bean instead of customer DAO for creating and maintaining account. Maybe Cade assumes that container managed security will be used, so details of creating accounts will be specified later (will LDAP or database table hold user names/passwords etc.)

Shopping cart will probably be maintained with HTTP session, so it is not actually a component to be shown in the Catalog component diagram.

The assigment tells us to show all J2EE components in the component diagram, so also entity beans should be there. But of course, you don't have to use entity beans, this is your decision. Also you could use stateful session beans, or just let the web or Java application maintain the state...

Tomi
[ August 24, 2004: Message edited by: Tomi Tuomainen ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic