Hi, it turns out that new methods will be needed for UML2, and even some of the existing ones have sometimes a different meaning in UML2. Example: getSpecification(handle). In UML2, this method is applicable to a behaviour (e.g. a method) and returns it's behavioral feature (e.g. an operation). But in the current implementation, we apply this method to operations!
Different usage of the model subsystem will require a lot of if-Statements in ArgoUML, checking for Model.getFacade().getUMLVersion(). Is this the right way to go? (As I said before, I'd prefer to abandon a release that both supports UML1 and UML2, so NO such if-Statements, is this indiscutabel?) For methods only used in either UML1 or UML2, I'd propose to have them both in the model subsystem, and then let the appropriate "wrong"/unused method throw a new kind of Exception that indicates that this method is not intended to be used in the respective UML version. Probably a NotSupportedInThisUMLVersionException (or maybe two different exceptions for UML1.x and UML2.x). The benefit: later the model subsystem can be cleaned more easily for no longer supported UML versions. What do you think? I'd like to have an agreement soon, because this blocks further work on the UML2 support. Thomas -- 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=1593026 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]]
