Creating an "XSDElement" attribute with a script: no tagged values

[Guillaume]

Hello,

I'm working on a script to create XSDelement stereotyped attributes within an existing XSDcomplexType class.
Despite the fact that the attribute stereotype is set to XSDelement, it doesn't have any tagged value.

I attempted to run the SynchProfile from the script (see below) but it doesn't work. I noticed that Synchronize Stereotype is not available from the toolbox.
e.g.

Code: [Select]

Repository.CustomCommand("Repository", "SynchProfile", "Stereotype=XSDelement;");
Do you know if there's a way to sort this? The only workaround I identified is to manually create the tagged values but it's a bit cumbersome.

Thanks

[qwerty]

I guess it would belong to some profile. You have to endeavor which one. Just grep in the MDGTech folder inside EA program files.

q.

[Guillaume]

XML Schema is part of the Core Extensions MDG so I understand the definition is built in EA.
I ended up manually creating the tagged values under the XSDelement attributes which worked ok.

[qwerty]

I'm a bit puzzled. Since XSD* is bound to no profile (but some wild EA-internal stuff) it does also have no stereotype properties since these are bound to/defined by profiles. So which "tagged values" are you expecting to see?

q.

[Geert Bellekens]

That seems to be a bit of a weirdo

I did a little test and found that the XSDElement (of the out of the box stereotype) doesn't have a profile
t_xref says this: @STEREO;Name=XSDelement;GUID={7C6052D4-A37C-43d0-B763-3F1281A402DF};@ENDSTEREO;

However it automatically creates these tagged values
- anonymousRole
- anonymousType
- default
- fixed
- form
- nillable
- position

there is also a UML profile for XML schema available for download from the sparx website.
If you use that instead of the default XML schema element you might be able to get the correct tagged values by specifying the fully qualified stereotype.

Geert

[qwerty]

Makes me wonder why they left over that internal mumbo jumbo if there's an official profile. Or rather it makes me wonder why it makes me wonder.

q.

[Guillaume]

I got the same results as Geert and ended up creating the tagged values on the XSDelement stereotyped attributes, including the enum values + descriptions when applicable.

Thanks