Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: IIS7 ASP Response object incompatible with MSXML transformNodeToObject

From: "Anthony Jones" <Ant@------------.--->
To: NULL
Date: 8/9/2008 7:04:00 PM

"Martin Honnen" <mahotrash@y...> wrote in message
news:ey43eWk%23IHA.5392@T......
> Anthony Jones wrote:
>
> >>> xml.documentElement.transformNodeToObject xsl, Response
>
> >>> The above works fine on IIS6 and below.  On IIS7 however it fails with
> >>> 0x80004001 Not Implemented on the transformNodeToObject.
>
>
> > This does appear to be
> > specific to the use of transformNodeToObject and the Response object.
>
> As long as you want to create XML with the transformation you could
> first transform to an MSXML DOM document and then save that to the
> Response object. But writing HTML or plain text as the transformation
> result to the Response object does not seem possible then which is quite
> a breaking change.
>


Exactly, code isn't going to migrate to IIS7 without modification.
Fortunately for myself my real world stuff uses a library so I need only
tweak the library with a workaround, whenever I can come up with one.

For others this could be a more painful experience.  I'll try to dig down
further, currently its not clear whether the problem is in SP10 of MSXML or
IIS7s ASP Response object.

-- 
Anthony Jones - MVP ASP/ASP.NET




transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent