Subject:is this a feature or a bug? Author:Kent Reed Date:22 Nov 2004 05:40 PM
Just today, I downloaded and installed an evaluation copy of Stylus Studio XML
Professional Edition (SSXPE) - version 6.0 build 212H.
On the theory that I should be able to push buttons without breaking anything, I
loaded an XML schema I had on hand. The file loaded just fine and I traipsed
through it in Text, Tree, and Diagram mode. However, when I click on the
Documentation tab, SSXPE goes into an endless loop displaying a Microsoft
Windows pop-up text-box which reads
'Encountered an I/O error in URL "file:///c:/Documents and
settings/Administrator/Local Settings/Temp/ex.xsd": c:\Documents and
Settings\Administrator\Local Settings\Temp\ex.xsd was not found.'
When I click on OK, it loops back to the same message.
I found only two ways I can break out:
-I can use Task Manager to kill Stylus Studio. This is an ugly solution.
-I can copy the missing file ex.xsd to the location indicated, in which case SSXPE
takes off, processing the documentation. This isn't such a great solution, either
(for example, I wasn't given a chance to set the include/import defaults as has been
described in other messages in this conference).
Granted, I should have read the docs (and possibly the messages on this message
board but how would I know what I was looking for before I ran into a problem?)
before I started exploring the schema, but I don't believe production software
should behave like this. It shouldn't be so hard to break out of the loop and return
to the previous, or some other known, state.
The schema file in question begins with the declaration
Subject:is this a feature or a bug? Author:Roger Powell Date:01 Dec 2004 07:44 AM
I have the same version as you but I've encountered no such problem, with one
exception, I never ever use the .NET validator. It has gone into infinite
loops before whereas all the others performed perfectly.
I have never had a problem with the documentation feature.
Try going through the different validators, starting with XSV (XML Schema
Validator) but leave the .NET one till last!!