Win a copy of Microservices Testing (Live Project) this week in the Spring forum!
  • 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 ...
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Coarse-grained entity beans and UML

Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello fellow ranchers,
Any thoughts, opinions, or truths you could provide on the following subject will be much appreciated!
I'm modeling an entity bean that has dependent objs on a class diagram, but am unsure how to stereotype the dependent objs. I've done a lot of reading on the subject, but am still unsure.
In short, I have one class, THE entity bean itself which is stereotyped as <<entity>>... I've considered stereotyping the dependent objs as <<entity>> as well, and just explaining that they are dependent objs of a coarse-grained entity in my design document. I've also considered stereotyping them as <<persistent>> (a generic stereotype I found in the UML spec), or not stereotyping them at all in the diagram.
Is there any standard or preferred way to depict this relationship visually?

Also, while I'm at it, what about the <<control>> stereotype -- in my Class Diag, I am planning on stereotyping all classes that will be Session EJBs as <<control>>. What about classes that are not going to be session EJBs, but *do* sometimes manage other objects (i.e., event handlers in the EJB Command Pattern, like in Petstore). Should these also be stereotyped as <<control>>, or is that misleading/overkill?
Thanks, and cheers,
    Bookmark Topic Watch Topic
  • New Topic