Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Mauricio Moya (Arquesoft) on July 28, 2018, 05:38:53 am

Title: SOLVED: Connector from custom profile rendered as Profile::Stereotype
Post by: Mauricio Moya (Arquesoft) on July 28, 2018, 05:38:53 am: I have a MDG based on a profile containing only connectors. When I create a new connector between elements, the stereotype in the connector is shown as <<MyProfile::MyStereotype>> instead of only <<MyStereotype>>.

Previous versions of MDG (a year ago) had generated <<MyStereotype>> connectors. It is supposed we have not made any change in the profile definitions, but now the connectors are generated as <<MyProfile::MyStereotype>>.

Any ideas what could be changed? (I've already checked any custom stereotype in the UML Types window.)
Title: Re: Connector from custom profile rendered as Profile::Stereotype
Post by: Paolo F Cantoni on August 06, 2018, 03:53:52 pm: Have you run a file comparator (such as BeyondCompare) over the two versions? Where things break for us, we carefully compare the working vs non-working version and try to "suss out" what broke.

Paolo
Title: Re: Connector from custom profile rendered as Profile::Stereotype
Post by: Geert Bellekens on August 06, 2018, 04:05:31 pm: Try it on a new model with no other MDG's or add-ins enabled.

Geert
Title: Re: Connector from custom profile rendered as Profile::Stereotype
Post by: Mauricio Moya (Arquesoft) on August 06, 2018, 10:15:29 pm: Quote from: Paolo F Cantoni on August 06, 2018, 03:53:52 pm
Have you run a file comparator (such as BeyondCompare) over the two versions? Where things break for us, we carefully compare the working vs non-working version and try to "suss out" what broke.

Paolo

The problem is the size of the model. It is a DMBS based model and it is about 1Gb in size.
Title: Re: Connector from custom profile rendered as Profile::Stereotype
Post by: Mauricio Moya (Arquesoft) on August 06, 2018, 10:51:08 pm: Quote from: Geert Bellekens on August 06, 2018, 04:05:31 pm
Try it on a new model with no other MDG's or add-ins enabled.

Geert

Great idea! I have just test it in a new EAP file and it works well. So, I rechecked the original model and I found some stereotypes (in UML Types) with the name "MyProfile::MyStereotype". So I just delete them and this solved the issue.