Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ken.norcross

Pages: 1 ... 3 4 [5]
No project template package, brand new empty EAP file.

Smilies disabled, thanks :)

I don't know why but I am getting duplicate tagged values when creating a profile that extends a non-uml element.

The xml for the profile element is pretty plain and simple:

<Stereotype name="Report" notes="" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0" generalizes="BPMN2.0::DataObject" baseStereotypes="BPMN2.0::DataObject"/>

I have reduced my test case to as simple as possible. New EAP file, new MDG model from the wizard, a single stereotpye as defined above, a single toolbox with one item, create the MDG xml using the wizard, import the technology, create an instance, and I get doubled tags.

The tags being duplicated are the BPMN2.0 tags. They show up under the BPMN2.0 category, and then again under the plain "Tagged Values".

I have given up trying to fix this, and have written a script to remove the extra tags.

Is this a bug or am I doing something wrong? I have reduced it to such a simple case I can't see anything wrong.

Hi all,

Still trying to work through creating a profile that extends non-uml profile elements.

My example is extending BPMN2.0

In the instructions it states to:
  - drop a metaclass on the diagram, and in the "extend metaclass" dialog that pops up, go to the last tab and find the non-uml stereotype you want to extend
  - using the Add Stereotype helper in the toolbox, define your stereotype, set the name, and do not pick a metaclass
  - create a generalize relationship from your new stereotype to the non-uml stereotype/metaclass

This is fine and so far (basically) works, but my question is:

 - How do you then use all of the useful features that are available and stored as attributes in a true metaclass? Without setting a metaclass for your stereotype there is no option of setting these features.

I have tried 2 workarounds, but I am running into so many unexplainable quirky results I want to check if anyone has a solution.

Attempt 1: I have tried adding the true metaclass for the non-uml stereotype and having the non-uml stereotype extend the metaclass.

So for example:

MyML::MyStereotype  --generalizes--> BPMN2.0::DataObject --extends--> UML::Artifact

Attempt 2: Add the true metaclass, and have my stereotype directly extend it

For example:

MyML::MyStereotype --generalizes--> BPMN2.0::DataObject
MyML::MyStereotype --extends--> UML::Artifact

Both styles make the metaclass properties/feature available in the profile helper when editing MyStereotype, and both seem to provide similar results, but I am wondering if there is a correct way to do this.

As I mentioned I am running into wierd quirky results when testing my profile, so I want to make sure I am doing this right.

(quirky results like: tagged values being duplicated; some BPMN elements draw their decorations properly, some do not; etc.)

Pages: 1 ... 3 4 [5]