Extending BPMN stereotype doesn't work (properly)

[Geert Bellekens]

My client needed a special type of BPMN 2.0 messages with some extra information -> Functional Information Stream
So what I did was create the stereotype «FIS» that specializes BPMN 2.0::Message.

So far so good, I added my extra attribute and a shapescript to differentiate «FIS» from a regular Message

This all worked fine up until we needed to model messageFlows. The tagged value messageRef only accepts BPMN2.0::Message stereotypes, but doesn't allow to select my «FIS» stereotype (which IS a BPMN2.0::Message)

So bye bye elegant solution, back to adding random tagged values with a script to a subset of all BPMN Messages 

Reported as bug.

Geert