Thanks to Dave and Brett for reporting this CF5 / MSXML bug - I've copied
the discussion below for those of you who missed it the first time.
1. Can any list members from Allaire/Macromedia comment on this? Is it a
recognised problem, and should we expect a patch?
2. As a temporary workaround I've started writing a Windows Scripting
Component (WSC) to act as a wrapper for the XSLTemplate interface: the
theory is that CF could call this scripted COM object as an alternative to
the native MSXML object and bypass the apparent CF5 naming restriction. I
haven't got it working yet... does anyone have any experience of using WSC
COM objects from within CF? Or does anyone have a better idea?
Best wishes
Tom
-----------------+
tom dyson
t: +44 (0)1608 811870
m: +44 (0)7958 752657
[EMAIL PROTECTED]
http://torchbox.com
> -----Original Message-----
> From: David Maddison [mailto: [EMAIL PROTECTED]]
> Sent: 13 July 2001 16:17
> To: [EMAIL PROTECTED]
> Subject: RE: [cf-xml] CF5 Warning
> OK, we've both tried exactly the same things, and come to the same
> conclusion, at least I'm not going mad! I was also going to conclude that
> it must be a bug in the way CF5 talks to COM objects.
>
> Pity because I've got two choices. On the one hand I use XSL a lot,
> especially the XMLDump tag which dumps an XML document out using the IE type
> stylesheet. On the other hand I need the QofQ feature of CF5 for my
> XMLQuery tag, that allows you to query an XML document using SQL.
>
> Oh well, I'll report it to MACR, and keep an eye on the forums.
>
> Dave
>
>>> -----Original Message-----
>>> From: Brett Suwyn [mailto:[EMAIL PROTECTED]]
>>> Sent: 13 July 2001 16:02
>>> To: [EMAIL PROTECTED]
>>> Subject: RE: [cf-xml] CF5 Warning
>>>
>>>
>>> I've spent a few hours working on this problem and still have not been able
>>> to use the XSLTemplate interface in CF5 due to this problem.
>>>
>>> I am getting the same error as you are receiving. From the TypeLib viewer
>>> the stylesheet "property" is registered as a method expecting a XMLDOMNode
>>> as input, but that throws a different error, I tried it with a freethreaded
>>> DOM node, and tried every different example I could find using this
>>> interface. It seems to me that this is a valid bug in CF5.
>>>
>>> If anyone finds a solution (or takes it to Macromedia) to this please post
>>> your results to the list,
>>>
>>> -Brett
>>>
>>> |> -----Original Message-----
>>> |> From: [EMAIL PROTECTED]
>>> |> [mailto:[EMAIL PROTECTED]] On Behalf Of
>>> |> Maddison, David
>>> |> Sent: Friday, July 13, 2001 10:36 AM
>>> |> To: [EMAIL PROTECTED]
>>> |> Subject: RE: [cf-xml] CF5 Warning
>>> |>
>>> |>
>>> |> Actually after futher analysis, it appears to be a change
>>> |> in the XSLT interface. We have a tag XSLStyleSheet which
>>> |> loads up a pre-compiled stylesheet.
>>> |>
>>> |> In order to use the XLS processor, you create an
>>> |> MSXML2.XSLTemplate and set the stylesheet property to a
>>> |> DOM holding your stylesheet. Under CF4.5 with MSXML3 SP1
>>> |> the following worked :
>>> |>
>>> |> <CFSET xslt.stylesheet = xom>
>>> |>
>>> |> However this now breaks under CF5 with :
>>> |>
>>> |> Error building an argument list for: STYLESHEET
>>> |>
>>> |> Which sort of means it's expecting a function call??
>>> |> Mmmm, I'll do some more work on this and send out my
>>> |> findings. As you've said the parser seems to be working
>>> |> fine, just the XSLT seems to break.
>>> |>
>>> |> Dave Maddison
-----------------------+
cf-xml mailing list
[EMAIL PROTECTED]
http://torchbox.com/xml
