• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

Do we need to drow DAO and entity bean?

 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My work stops at EJB session facade level.
So the whole diagram is very simple and clear.


I feel there is no need to draw persistent related thing in architecture design.

Any commments?
 
Ranch Hand
Posts: 102
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Finland,

I have drown the entity bean and DAO in component diagram. I dont think that we need draw each entity bean and DAO in component, but the detail description for each entity bean and DAO is a must. it is my understanding to the assignment.
 
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Finland Finland:
I feel there is no need to draw persistent related thing in architecture design.


Don't know how detailed the diagrams should be, but it should visible from your diagrams, what persistence mechanism has been chosen and why it works.

regards,
Harbo
 
reply
    Bookmark Topic Watch Topic
  • New Topic