> 2) Do as they appear to have done at > http://www.xml.com/pub/a/2002/08/07/wxs_uml.html and use a > class with an <<Enumeration>> stereotype rather the an actual > stereotype. My suspicion that that is what they are showing > is based on the capitilazation of <<Enumeration>> as opposed > to the lowercase <<enumeration>> keyword.
I presume Bob meant "rather than an actual *enumeration*" above and that would be my suggestion as well -- use a Class with an <<Enumeration>> stereotype. The two figures in the article are inconsistent in that one uses <<Enumeration>> and the other uses <<enumeration>>, but even with the <<enumeration>> version is impossible to tell visually whether it's what UML calls a "keyword" or a real stereotype (something I consider to be a flaw in the way UML has specified this). It seems that using a Class with an <<Enumeration>> stereotype is actually fairly common. The other reason this gets used is that a UML Enumeration element does not have rich enough semantics to model the semantics of a Java enum. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
