Specify whether to quit XMLSpy.
Once all XML schemas have been processed and all diagrams generated, XMLSpy is not needed any longer. Then, XSDDoc issues a command to finish the XMLSpy integration. What will happen with the running instance of XMLSpy depends on the setting of this parameter:
true
(selected)
This is the default mode (and default setting of this parameter).As soon as the finishing XMLSpy command is issued, the integration calls an XMLSpy API method to quit XMLSpy and waits until it returns. After that, the processing of XSDDoc templates (that is the generation of documentation) continues.
If you run XSDDoc again (e.g. while using the generator GUI) with XMLSpy integration enabled, a new XMLSpy instance will be launched and so on.
One problem with this mode is that on Linux/Wine quitting of XMLSpy may raise an error (or even hang JVM). In that case, you may try to unselect this parameter.
false
(unselected)
The running instance of XMLSpy won't be quitted. The processing of XSDDoc templates continues as normally.See Also Parameters:If you run XSDDoc from the generator GUI and then run it again (with XMLSpy integration enabled), the same XMLSpy instance will be reused.
When DocFlex/XML exits (that is the JVM running it), its use of the XMLSpy instance will be released. However, the XMLSpy process itself will remain in memory running. If "Integrations | XMLSpy | Show XMLSpy" parameter was selected before that, the XMLSpy IDE will be visible still. So, you can use it and quit by standard means.
On Linux/Wine, releasing XMLSpy instance probably doesn't work smoothly again. But then, the Wine itself quits, so you won't see anything. (The full XML schema documentation with the diagrams will be ready at that).