I've just been looking at the use of Profile.addProfileDependency and where it is called. I was wondering how much profiles need to know about eachother internally or whether this relationship should be held somewhere extrernal to the Profile itself.
I see that NormalProfileCpp and ProfileJava have different constructors for this. NormalProfileCpp has knowledge of the UML profile built into its default constructor. The default constructor of ProfileJava is unused. Instead it uses a constructor where the UML profile is passed in as an external argument. Which is more correct? Has it been tested how well the system reacts to the IllegalArgumentException coming from addProfileDependency if a circular dependency is introduced? Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
