Book a Demo

Author Topic: MDG Technology question  (Read 2393 times)

Ashton

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
MDG Technology question
« on: July 01, 2011, 04:29:39 pm »
Hi guys,
I’m trying to create my fist proper profile, and by proper, I mean I’m giving it toolbars, diagram types and stuff like that to be imported as an MDG technology as opposed to before when it would only be a single structure that I could import as a profile in my "project resources" tool box. My problem now is that my connections that I’ve defined in the profile core are not behaving like connections! Can’t imagine what the problem might be since it works when I add the connection definitions as a simple resource. The problem happens when i put them in a toolbox.
Can anyone give me a clue where to look for the problem?
« Last Edit: July 01, 2011, 04:30:54 pm by Ashton »

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: MDG Technology question
« Reply #1 on: July 01, 2011, 04:46:18 pm »
In your toolbox profile you will have a «stereotype» class that extends a «metaclass» class named "ToolboxPage". Your «stereotype» class will have an attribute for each toolbox item, named something like "MyProfile::MyStereotype(UML::ConnectorType)" where "MyStereotype" is the name of the stereotype to be applied to the connector, "MyProfile" is the name of the profile in which "MyStereotype" is defined, and "ConnectorType" is from this list.

Also, don't import the technology into the Resources tree (and if you already have, delete it from there). Instead, go to Settings > MDG Technologies and add a path to the folder that contains your technology.

If it still isn't working, send your technology XML file to Sparx Support and they will be able to see what's going wrong.
The Sparx Team
[email protected]

Ashton

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: MDG Technology question
« Reply #2 on: July 04, 2011, 09:44:52 am »
That was excellent KT
the problem was that I was casting my connector to a class in (UML::Class) and that’s why it was behaving like one. I changed that to Association and everything is fine now.
 cheers