Hi! -------- Original-Nachricht -------- > Datum: Fri, 27 Mar 2009 08:43:52 -0400 > Von: Tom Morris <[email protected]> > An: [email protected] > Betreff: Re: [argouml-dev] Extend CodeGenerator interface to let module find > it\'s classes?
--<snip>-- > Couldn't this be implemented as an option internal to the module > itself? Then the user could say "generate all classes" and the module > could filter those that it knows how to generate. Not in any cases. In case of the SQL module, we could enforce the use of the DB profile and ignore classes without a 'Table' stereotype as an example. But in some cases there might be good reasons not to use a stereotype (there could be classes that are actually tables _and_ Java classes as example). In other cases, it's not necessary clear from the diagram if someone wants to create Java, C++ or maybe PHP from a class? --<snip>-- > > If it did turn out to be something requiring an API change, there are > ways to do it without breaking existing modules. Something which > broke all existing modules would be very bad. I know...that's why I posted here before committing any modifications... :-) Ciao, Andreas -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1445624 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
