This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XMLDOM xml to html translation problem
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] XMLDOM xml to html translation problem
- From: Joseph Coffman <jcoffman at rospo1 dot bbn dot com>
- Date: Wed, 22 Aug 2001 13:54:27 -0400
- References: <5.1.0.14.2.20010822111220.00a89de0@localhost>
- Reply-To: xsl-list at lists dot mulberrytech dot com
thanks all, I installed msxml3 and xmlinst.exe and everything's working
like butter. you all rock, thanks!
At 12:02 PM 8/22/2001 -0400, you wrote:
>This is a common problem. You have a mismatch between the stylesheet
>language and the processor. This is indicated by the xsl namespace declared
>in the stylesheet. There are two possibilities:
>
>1) The stylesheet is for xslt 1.0, but your server has an old version of the
>Microsoft xml processor (or it has msxml3.dll but not installed in "replace"
>mode"). This is the most likely case. This is happening if the namespace is
>
>xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>
>2) The stylesheet is for the obsolete Microsoft language they called "XSL",
>but you have a newer version of the processor installed. In this case, the
>namespace would be
>
> xmlns:msxsl="http://www.w3.org/TR/WD-xsl
>For case 1) you have to get msxsml3.dll from Microsoft and install it, then
>get xmlinst.exe from them and run it to cause the new processor to actually
>be used by your server.
>For case 2), you need to rewrite the stylesheet using xslt 1.0. This will
>go beyond changing the namespace.
>Cheers,
>Tom P
>[Joseph Coffman]
> > I've searched high and low for a solution to this seemingly simple
> > problem. I'm using ASP on a win2000 server machine running IIS5.0 and
> > attempting to translate an xml to html using an xslt script I have
> > written. I have found code in numerous places doing this translation
> > serverside using the XMLDOM transformNode method. I have attempted to
>copy
> > the code but as yet have been unable to make it function correctly.
>Rather
> > than printing the translated HTML, it prints the xsl document to the
>client
> > browser. Included below is the actual code being used, I would appreciate
> > any feedback.
> >
> > thanks
> >
> >
>****************************************************************************
>*
> > <%@ LANGUAGE="VBSCRIPT" %>
> > <!--#include file="adovbs.inc"-->
> >
> > <%
> > resume_file = Request.querystring("resume")
> >
> > xml_file = Server.Mappath("xml/" + resume_file)
> > xsl_file = Server.Mappath("xml/resume.xsl")
> >
> > set xmlPage = Server.CreateObject("Microsoft.XMLDOM")
> > xmlPage.async = false
> > xmlPage.load(xml_file)
> >
> > set xmlStyle = Server.CreateObject("Microsoft.XMLDOM")
> > xmlStyle.async = false
> > xmlStyle.load(xsl_file)
> >
> > Response.Write xmlPage.transformNode(xmlStyle)
> > %>
> >
>****************************************************************************
>*
> > At this point the client browser receives the xmlStyle page, NOT the
> > translated page. Any idea why?
> >
> >
>
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Joseph Coffman
703 284 8624
703 486 4567
BBN Technologies
A Verizon Company
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list