I'm confused about the difference between something being a "stereotype" and being a "superclass" in UML. Let's say I want to create a diagram involving a "WidgetMaker." WidgetMaker is clearly an Actor so the UML standard is to stereotype it actor: <<Actor>> WidgetMaker But I grew up programming in the Java/Ruby/C++ world. In that ...
Is there a way to get a reference to Microsoft.VisualStudio.Uml.Profiles.IStereotype interface in a t4 template? I mean IStereotype that stores the definition of the UML stereotype, and not IStereotypeInstance that holds the actual value. I tried something like this, but the ApplicableStereotypes enumereation is empty. void WriteClassAt...
When moving to Spring 2.5.x I found that it adds more stereotype annotations (on top of @Repository from 2.0): @Component, @Service and @Controller. How do you use them? Do you rely on implicit Spring support or you define custom stereotype specific functions/aspects/features? Or is it predominately for marking beans (compile time, conce...
I'm not sure where to do database lookups for Spring controllers. It seems to make sense to use the Spring @Service stereotype and create multiple "services" to provide lookup support to controllers rather than doing lookups directly in the controllers. Is this correct or is there a more appropriate place to perform database lookups? ...
What's the difference between declaring the TestController with the Spring Controller stereotype like this: import org.springframework.stereotype.Controller; //... @Controller @RequestMapping("/test") public class TestController versus as a subclass of the AbstractController like this: import org.springframework.web.servlet.mvc.Abstr...