The problem is I really don't understand the contradictions I see in
the UML spec and how can I tackle this.

MagicDraw chose the same solution that you did originally. It does
seem to go against the UML spec and when a binding is created it seems
strictly speaking to be ill-formed as the bound argument should be the
same class type (or descendant of) the parameter type.

However in all other respects it is possible to store the data
required and to visualise the model to the user in a way that makes
sense to them.

MagicDraw are OMG members and will be getting direct input from OMG on
how to interpret the spec so I would expect them to have taken an
acceptable way but I would have hoped to have some example from
another UML1.4 tool.

Does anybody have access to any other UML1.4 tools to see what their
XMI looks like.

About the only thing I can find to support use of Parameter inside
TemplateParameter is this section in the spec -

<snip>
4.5.2.31 Parameter
A parameter is an unbound variable that can be changed, passed, or
returned. A parameter may include a name, type, and
direction of communication. Parameters are used in the specification
of operations, messages and events, __templates__, etc.
</snip>

So Parameters are used in the specification of templates - however
that does seem to be contradicted elsewhere in what I have
interpreted.

If we don't have a definite agreed way to move forward for this then
it look like TemplateParameters may not make the next release.

2009/12/14 Alexander Lepekhine <[email protected]>:
>> Lets not forget template binding. Did you do any work for the Alexander?
>
> I remember but can we write binding not knowing what template parameter is?

My point was simply that releasing TemplateParameters before binding
is available may well be of little use.

Bob.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2430348

To unsubscribe from this discussion, e-mail: 
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email: 
[[email protected]]

Reply via email to