This will leave all diagrams closed after project load but increases speed and uses less memory. Better to turn off diagram loading by Main Menu-Options - Environment - General - Save/Load - Diagram load mode - Do not load diagrams.
Thank you for your report.There are few recommendations how to improve performance working with big projects:ġ. Bug fix will be included in MagicDraw 16.9 beta. We have investigated this problem and reproduced it. Subject: Re: MagicDraw 16.8 XML schema generation - XSDinclude problem To: Decker, Brian Cc: MagicDraw Support Team Until then I'll continue my work in 16.8, turn off the Syntax Checking steps, and manually insert the "include" lines I need where I need them in the generated XSD files.įrom: MagicDraw Support Team Thursday, J5:10 AM I'll be downloading the 16.9 Beta as soon as I can.
Thank you for the update and agreement that a problem exists. I will also submit this to and attach the model. I am interested in any information that may get me over this issue since I am at a dead stop right now with my project. Or possibly the usage of XSDinclude inside the XML models has changed. So I'm curious if something is known to be problematic with XSDInclude directives or use of referenced files in this version. Like I said, I've never had these errors with previous versions of MD. Syntax checking was made on temporary file file:///C:/Data/Local/Modeling/MagicDraw/XMLTest%202010/MySubsystem/Įrror: 11:76: src-resolve: Cannot resolve the name 'my:ComplexUsefulType' to a(n) 'type definition' component.Įrror: 12:69: src-resolve: Cannot resolve the name 'my:OneUsefulType' to a(n) 'type definition' component. When I check syntax or attempt to generate against System.xsd however, I get errors that types cannot be resolved: for NamespaceCommon.xsd, Check Syntax operation is successful, and Generate operation produces correct NamespaceCommon.xsd file output in the correct directory.
Now under 16.8 using my my Code Engineering Sets: System.xsd has an XSDinclude directive to NamespaceCommon.xsd and creates an AnonymousType that has Attributes that are of types from NamespaceCommon.xsdĪll files checked and generated with no problems under prior versions of MD. NamespaceCommon.xsd defines three types "OneUsefulType, which is an enumeration, "ComplexUsefulType" which contains a string and an instance of OneUsefulType, and ComplexTypeWithExternals with includes an instance of a type referenced in a schema component of "" is the namespace where I am working, and it contains two XSD files, NamespaceCommon.xsd and System.xsd "" contains a pre-defined types inside "ForeignSchema.xsd" - assume this was a library that I Reversed into my model from existing XSD files All files reside in the project directory for simplicity Under MD 16.8 / UPDM 16.8 SP1 when I open my project and check syntax or generate XSD files I now get errors about referenced types in an XSD file that has an XSDInclude directive to another schema in the same namespace.
I've been able to open a XML project with different versions and check syntax and generate XSD files with no errors. I did not have the problem that I describe below with previous versions of MagicDraw. I also have UPDM 16.8 SP1 installed but don't believe it pertinent to the XML Schema modeling capabilities. I may be having a problem with XSDinclude processing or code engineering/generation in Magic Draw 16.8.