What should be the stereotype of JSF backing beans in class diagram - <<control>> OR something else?Are they controller objects or model objects in MVC?
Rajan Choudhary wrote:I guess, you could use any valid stereo type like BackingBean or ManagedBean or ModelBean etc. Now, I am not sure if I am doing wrong or right but I am putting lot of info in stereo type in the sequence diagrams for the messages. For example, "User Clicks Submit" or User Navigates to bla blah page etc are done with stereo types. Is that ok? Need your feedback.
I reckon you should use UML notes for that instead of stereotypes. Also there is no need to go too detail on this. Keep it high level
Kumar Amit wrote:Thaks Ranga.
Any suggestion on stereotype for Stateless Session Beans (implementation) class? Mark cade has used "@stateless" in his book. Also what should be the stereotype for the business interface of the SLSB?
If we start showing remote/local interfaces, home interfaces and then implementation classes, I am wondering how would the class diagram look like
As other members have suggested, I am showing only implementation ejb class with public methods (no private method). I think, that's enough.
Didn't tried using @Stateless but used <<SLSB>> and provided in the legend(foot notes) that it's Stateless Session Bean as my diagram was getting cluttered due to too big stereotype name. I prefer consistency - if using @@Stateless at one place why not @ or some other special symbol for other stereotypes?
There is no harm showing multiple stereotypes for the same class.