Hi Tom,
> > > The database module uses <<PFK>> for modeling a column (class attribute) > > that is both foreign and primary key. > > I'll resist asking why this isn't two separate stereoypes (e.g. <<PK>> > & <<FK>>) if there are two separate sets of semantics We have <<PK>> and <<FK>> for modeling a column that is either primary or foreign key respectively, but when a column is both primary and foreign key, we use <<PFK>>. > > Does anybody know how to preload a module with new stereotypes? [...] > > How to add <<PFK>> to available stereotypes list for attributes? > > Have a look at some of the recent postings from Luis concerning the > C++ module's profile. New stereotypes and their associated tag > definitions are one of the key uses of the profile mechanism. > Multiple profiles can be in use at any given time and they can either > extend a bundled profile or just add independent functionality. > > The default ArgoUML 0.24 profile has been split into separate three > separate pieces: UML 1.4 Standard Elements (from Appendix A of the > spec), Java specific elements (java.lang.* datatypes, etc), and > ArgoUML elements (documentation, author, since, etc tags). The C++ > profile is part of the C++ module, but will also get distributed with > 0.26 since the C++ module is bundled. I'd recommend creating an > argouml-db profile with any stereotypes, tagged values, and datatypes > that you require. Also, be careful about assuming that things like > the Java datatypes will be available since the user has the option of > turning off any and all profiles. You should document which profiles > you assume will be available. > I will familiarize myself with using the profile and do like you suggested. > Having said that, this is a post-0.24 enhancement and the last time I > tried to build argouml-db against the current ArgoUML SVN sources, I > had to change some things to get it to compile. Are you maintaining > separate 0.24 and 0.26 branches or is the module 0.24 only right now? > (Yes, I know we shouldn't be breaking things at such a rapid pace, but > that's a separate issue) > We have been using only 0.24 and hoping to switch to 0.26 when it becomes available. Thanks, Jules --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
