Anyone know of any issues with using and mixing use of the built in XSD/WSDL toolbox, transformation, and generation tools combined with importing the Sparx provided XSD UML Profile? The Profile seems to be required to use the scripting engine to create packages and elements in EA of the stereotypes included (XSDschema, XSDcomplexType, ...) through the API (to get all the proper tags and such). I'ld like to use both to leverage scripting for automating creation and population of XSD and WSDL stereotyped classes, packages, ... and the built in tools to perform generation and transformation and drag and drop from the toolboxes. But I also want to be sure I'm not creating chaos in the EA repository.
