I am generating X3P documentation with the Pro version and run into a bug (I think).
I have 4 XSD files that include each other. I generate documentation at top level, and it correctly generated 4 html files.
However the item links in "XML instance representation"....does not always link to the correct file, it often links to the "current" file instead of the file that contains the defintion.
I have included the 4 XSD files, together with the generated doc. please open amis_comm.xsd.html goto "command" open instance representation and click at e.g. "type_sequenceId "...this simpleType is defined in amis_types.xsd, but the url points to amis_comm.xsd.
I hope you can give me swift answer since this problem is holding up a delivery.
Subject:XML schema documentation generation. Author:jan iversen Date:18 Jan 2006 01:37 AM
ups I forgot the version number...it is 2006 Professional version Build 501f.
Both SearchIncludedSchema and SearchImportedSchema are set to "true".
Looking at my files the setup are
amis_extern incl. amis_comm incl. amis_elements incl. amis_types.
I always generate from amis_extern, and it generates 4 html files, so it is aware of the include files.
I have now testet a bit more, and the problem seem to be isolated in amis_comm when referencing amis_types....I have controlled that the "header" are identical built in all 4 files.
I also tried to generate documentation from amis_comm and amis_comm...html still contains wrong references for all types (located in amis_types) but are ok for all elements (located in amis_elements)...
The problem seems to manifest only for reference to AttributeGroup components.
For instance in the global element "reply" (amis_comm.xsd.html#element_reply)
the "Schema Component Representation" has a correct link to the
AttributeGroup but the "XML Instance Representation" hyperlinks to the simple types are incorrect.
You seem to be expert in xs3p stylesheet, so I allow myself to insert a small extra question.
I want to print the "manual" pages, and look for a way to get printed so that each element start on top of a new page (there is a bold seperator line, which basically needs to be replaced with a form feed), do you know of a intelligent way to do this ?