This week's giveaway is in the Programmer Certification (OCPJP) forum.
We're giving away four copies of Java Mock Exams (software) and have David Mayer on-line!
See this thread for details.
Win a copy of Java Mock Exams (software) this week in the Programmer Certification (OCPJP) forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Stereotype question

 
Luay Abdulraheem
Ranch Hand
Posts: 65
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear All,

What is the right way to represent a stateless session bean in Class diagram, stereotype <<@Stateless>> or <<Stateless>> ? same to <<@Entity>> or <<Entity>> ?
With or without '@' ?

Thanks in advance.
 
Mario Kerk
Greenhorn
Posts: 10
Android Java Ubuntu
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Luay Abdulraheem wrote:Dear All,

What is the right way to represent a stateless session bean in Class diagram, stereotype <<@Stateless>> or <<Stateless>> ? same to <<@Entity>> or <<Entity>> ?
With or without '@' ?


I think the most common way would be without the @ symbol (i.e. <<Statelss>>, <<Entity>>).

The @ symbol reminds me of Cades/Sheils's chapter 9 class diagrams where "annotations" (and not stereotypes) were used to show the same information. In that case the annotation was added inside a parenthesis next to the class name (e.g. "Bid (@Entity)") , so this might have been what confused you.

 
Krishna Jonnalagadda
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes <<stateless>> and <<entity>> is correct.

I have another question regarding the same.

How should we represent a local state less and a remote state less. Will it be some thing like this : <<local stateless>> or <<remote stateless>>

Can any one please clarify this ...?

 
Mario Kerk
Greenhorn
Posts: 10
Android Java Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Krishna Jonnalagadda wrote:
How should we represent a local state less and a remote state less. Will it be some thing like this : <<local stateless>> or <<remote stateless>>
Can any one please clarify this ...?


I think that UML allows the flexibility to introduce your own stereotype names, like "local stateless" or "remote stateless" as you have suggested. I don't remember of ever coming across the specific names, probably because it usually is not necessary to go into so much detail in a class diagram. But that's just the way I see it, I guess.
 
Happiness is not a goal ... it's a by-product of a life well lived - Eleanor Roosevelt. Tiny ad:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!