Invalid combination... for metaconstraint

[qwerty]

(Once again)

I have added a stereotyped relationship between a stereotyped ActivityParameter and a metaclass ActionPin (in both directions). The code looks like this:

Code: [Select]

<Stereotype name="activity parameter" metatype="Activity parameter" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="1" hideicon="0" generalizes="Noteable" baseStereotypes="Noteable">
<stereotypedrelationships>
<stereotypedrelationship stereotype="myProf::object flow" constraint="ActionPin;myProf::activity parameter"/>
</stereotypedrelationships>
<AppliesTo>
<Apply type="ActivityParameter">
<Property name="isException" value="false"/>
<Property name="isStream" value="false"/>
<Property name="_HideUmlLinks" value="True"/>
</Apply>
</AppliesTo>
</Stereotype>
Now, when I try to add that <<myProf::object flow>> EA croaks Invalid combination...blabla. Why on earth?

And please don't suggest me to turn of Strict Connector Syntax! I'm introducing metaconstraints in order to have a more strict check, not to be forced to have laissez-faire.

q.

[qwerty]

Seems like I have to send a support ticket for that?

q.

[Geert Bellekens]

Seems like I have to send a support ticket for that?

q.

Probably. All I can say is that this usually works fine for me.

Geert

[qwerty]

Thanks for the heads up. Maybe I try with some scratch again before turning to Sparx' support.

q.

[qwerty]

I made a scratch profile addition and that worked. Now I scratch my head to find out the reason...

q.

P.S. There's something fishy. I made a stereo constraint Act-Param -> ActionPin which worked. Switching direction did NOT give any addition in the QL dropdown. Also having set one to and one fro made both QL dropdowns empty. Just what I expect from EA: consitently inconsistent. Unless I get the gist of it this afternoon I'll report a bug.

[qwerty]

I gave up and sent a bug report. Will report here what the outcome will be.

q.

[qwerty]

Sparx support found the issue which is a bug in EA. Instead of ActionPin as metaclass you need to use Pin (which isn't in the list and needs to be created manually). Hope that this will be fixed, but the workaround seems to do no harm elsewise.

q.