SSDN - SS 4.5 103i bug?: Can't access xhtml DTD

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Topic

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Lee Humphries

Subject: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Lee Humphries
Date: 03 Nov 2002 11:01 PM

I use the attached XSLT to reprocess the html docs that stylus studio produces. It works fine when I use the internal XSLT processor but all of the other XSLT processors report various issues. These all seem to be related to not being able to open the xhtml1-strict.dtd specified by the source document (the HTML documentation file).

To test the XSLT just generate and save some HTML documentation from a schema using the documentation tab. Then run this XSLT over the resultant html file trying the various XSLT processors.

Regards, Lee

XSDDocumentor.xsl
XSD documentation reprocessor

Minollo I.

Subject: Re: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Minollo I.
Date: 03 Nov 2002 11:49 PM

I can't reproduce this problem, which makes me guess that the other
processors are hitting the same issue that we fixed a few weeks ago on
Stylus (remember the "authentication required" issue that you helped us
addressing?); probably the other processors are not properly handling the
same situation.

We will try investigating if there is anything we can do; at the very least
we can file this as an issue with owners of the other processors. Are you
experiencing the same issue with XalanJ, Saxon and MSXML .net?

Thanks,
Minollo

Minollo I.

Subject: Re: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Minollo I.
Date: 03 Nov 2002 11:54 PM

BTW, if you want to customize the way XML Schema documentation works, you
may find useful to directly modify the XSLT responsible for creating
documentation in the first place; you can find it in:
\bin\Plugins\schema-documentation

Once modified, Stylus will use the modified version; so you may want to
keep a copy of the original version.

Minollo

Lee Humphries

Subject: Re: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Lee Humphries
Date: 05 Nov 2002 12:25 AM

Hi Minollo,

>BTW, if you want to customize the way XML
>Schema documentation works, you may find
>useful to directly modify the XSLT
>responsible for creating documentation in
>the first place; you can find it in:
>\bin\Plugins\schema-documentation

I've tried this now instead (saves on the reprocessing). Here's a few other queries and comments though:
1. There's no option (from the documentation tab) to specify where the image files are to go. This meant I had to discard using the base_IMG_URL param. It also means I still have to run my script file to move all of the image files from their individual directories to the shared directory I want them in.
2. For me it would be nice if the default title in the documentation/options was the filename (sans extension).
3. I altered the PrintURI template so that it would add a link where the URI finished with an '.xsd'. That way I get links to all of the included/imported schemas.
4. I have one schema that acts as the ultimate 'container' for all the rest. When I run it directly through the x3sp XSL, it's completed in a fraction of a second. When I run it using the documentation tab it takes an incredibly long time (many minutes). It seems that all of the includes and imports are being resolved and images generated for every one, even though next to none of the images will end up in the final documentation. You only seem to need about 4 or 5 layers of includes/imports before the delay gets extremely large, especially if a common type library sits at the very bottom.

Ivan Pedruzzi

Subject: RE: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Ivan Pedruzzi
Date: 05 Nov 2002 11:30 PM

Hi Lee

> 4. I have one schema that acts as the ultimate 'container'
> for all the rest. When I run it directly through the x3sp
> XSL, it's completed in a fraction of a second. When I run it
> using the documentation tab it takes an incredibly long time
> (many minutes). It seems that all of the includes and
> imports are being resolved and images generated for every
> one, even though next to none of the images will end up in
> the final documentation. You only seem to need about 4 or 5
> layers of includes/imports before the delay gets extremely
> large, especially if a common type library sits at the very bottom.

These are all good points, we will try to address them for the next
update

Thank You for your feedback

Ivan

>
>
>
> To reply: mailto:stylus-studio-tech.5965@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
>

Lee Humphries

Subject: RE: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Lee Humphries
Date: 06 Nov 2002 11:59 PM

Hi Ivan,

Assuming I'm correct in my statement about all the images being generated for every included/imported/referenced schema. What would be really handy is to have the option to generate documentation for just the schema in question or for all schemas 'contained' by the current schema.

Having the option to generate a superset of the documentation would also really help in providing a source for reprocessing into a data dictionary / glossary.

Lee

Lee Humphries

Subject: Re: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Lee Humphries
Date: 04 Nov 2002 10:51 PM

Hi Minollo,

>I can't reproduce this problem, which
>makes me guess that the other processors >are hitting the same issue that we fixed a >few weeks ago on Stylus (remember the
>"authentication required" issue that you
>helped us addressing?); probably the other
>processors are not properly handling the
>same situation.

Yes, it does seem like that situation all over again. Here's one point of difference though. At this stage if I try running the XSLT against MSXML4 from the command-line I do get a different result. The XSLT runs down to the first XPath reference to something in the source document and then finishes processing at that point (like it doesn't understand the namespace prefix properly).

>We will try investigating if there is
>anything we can do; at the very least we
>can file this as an issue with owners of
>the other processors. Are you experiencing
>the same issue with XalanJ, Saxon and
>MSXML.net?

Here's what I get:
Xalan-J
java.lang.RuntimeException: java.net.NoRouteToHostException: No route to host: connect

Saxon
java.lang.RuntimeException: org.xml.sax.SAXParseException: Cannot read from http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd (No route to host: connect)javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: Cannot read from javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: Cannot read from http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd (No route to host: connect)

MSXML.net
(goes away for a long time, but doesn't do anything).

MSXML3 and MSXML4
External XSLT processing started...
Error occurred while loading document 'c:\WORKCARD\Integration\SCHEMA_REPOSITORY\Workcard\wcWorkSite-v1.0.html'.
Code: 0x80070005
Access is denied.
Error processing resource 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'.
...done

SaxonError.txt
Full Error Text from Saxon

Xalan-JError.txt
Full Error Text from Xalan-J

Minollo I.

Subject: Re: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Minollo I.
Date: 04 Nov 2002 11:45 PM

>...
>Yes, it does seem like that situation all over again. Here's one point of
>difference though. At this stage if I try running the XSLT against MSXML4
>from the command-line I do get a different result. The XSLT runs down to
>the first XPath reference to something in the source document and then
>finishes processing at that point (like it doesn't understand the
>namespace prefix properly).

Are you using the -xe option running MSXML4? That's the only case in which
I can run the stylesheet when the XML source is pointing to an unreachable
DTD. But then it works fine for me, so I don't know what the problem could be.
Also, trying to run the stylesheet you posted with any of the processors
when the DTD is reachable works fine for me.
When the DTD is not reachable, only the internal processor is able to
proceed without errors.

Minollo

Lee Humphries

Subject: Re: SS 4.5 103i bug?: Can't access xhtml DTD
Author: Lee Humphries
Date: 05 Nov 2002 12:28 AM

I decided to not bother with this particular line now, as it's a lot easier to just modify the XSL that produces the documentation instead.

I still have some comments and queries about it though (see above).

Regards, Lee

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

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 to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

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.