XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Nick LockeSubject: Documentation - prevent imported files also generating
Author: Nick Locke
Date: 26 Jun 2007 09:32 AM
The Schema documentation tool is excellent!

However, I am using it to save HTML documentation and have noticed that it generates documentation for imported files aswell as the actual file that I want.

For example, I have two XSDs - A and B, with A defined as an import within B. If I generate documentation for A, I get A.xsd.html as I would expect. But, if I generate documentation for B, I get both B.xsd.html and A.xsd.html.

I can see why this happens, but it is inappropriate in my situation. I have tried the various option settings, but none of them seem to affect this.

Can it be done?

Postnext
Alberto MassariSubject: Documentation - prevent imported files also generating
Author: Alberto Massari
Date: 27 Jun 2007 12:58 PM
Hi Nick,
we never thought it was useful generating the documentation with a part of the types excluded; would you mind sharing with us the reasoning behind this?

Thanks,
Alberto

Posttop
Nick LockeSubject: Documentation - prevent imported files also generating
Author: Nick Locke
Date: 28 Jun 2007 05:13 AM
Hi Alberto,

I guess I can workaround this simply by deleting the "extra" files that I don't need. However, an explanation, as requested:

My schemas will be shared with a number of target audiences, with the idea that people can only see the specific schema documents which are relevant to them. The saved HTML documents are stored on a web server (in a non web-accessible area). I then have a web page within my application which receives the request for a given schema, checks the authority and then streams the HTML file to the browser. I also have to keep the JPGs away from the web-accessible area, so my application intercepts the call for a JPG (checks authority again) and then serves the content.

In the links.xml file, I specify that all SchemaLocations actually point to the single web page in my application (with the schema id code included in the URL).

For ease of maintenance, each HTML schema is in its own subdirectory. So, when I generate the documentation, I get "spare" copies of the imported schemas in the subdirectory (spare because they already exist in the subfolder that they will actually be delivered from).

I guess, if I didn't have the schemas in separate directories, the problem would go away!

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.