This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
FW: MSXML and Namespaces ... not fully implemented (was RE: Has docum ent(string) in MSXML 3 (July preview) worked for any one?)
- To: xsl-list at mulberrytech dot com
- Subject: FW: MSXML and Namespaces ... not fully implemented (was RE: Has docum ent(string) in MSXML 3 (July preview) worked for any one?)
- From: sara dot mitchell at ps dot ge dot com
- Date: Thu, 7 Sep 2000 13:56:50 -0400
- Reply-To: xsl-list at mulberrytech dot com
- Sensitivity: Private
-----Original Message-----
From: Mitchell, Sara (PS, IT)
Sent: Thursday, September 07, 2000 11:02 AM
To: 'Eckenberger Axel'
Subject: RE: MSXML and Namespaces ... not fully implemented
(was RE: Has
docum ent(string) in MSXML 3 (July preview) worked for any one?)
Sensitivity: Private
Interesting -- although I don't think this is my problem (which
I am still trying to solve). Neither the document nor the stylesheet
are using namespaces.
I think that the problem is that MSXML is being invoked from
a script (JScript I believe) from inside XMetal. It loads my
XML document and XSL sheet and uses transformNode.
I believe the error is caused by a well known problem, that
the Base URI
is 'undefined' because all of this is happening in memory and
so MSXML doesn't know where to find the file with a relative path --
it's relative to nothing.
I've since been trying to find out how to pass a parameter to the
stylesheet (i.e., <xsl:param> at a global level), but can't
seem to find
the documentation on how to do this. (I've tried the MS SDK
documentation
and Mike Kay's book, but no luck.) I suppose I could literally
change the stylesheet in memory using Mike Kay's example, but would
prefer to do this with a method that will work in other XSLT
processors also as we have another downstream process that is going
to use XT.
Thanks for looking :-),
Sara
>
> > -----Original Message-----
> > From: Eckenberger Axel [mailto:Extern.Eckenberger@kmweg.de]
> > Sent: Thursday, September 07, 2000 2:01 AM
> > To: 'sara.mitchell@ps.ge.com'
> > Cc: 'xsl-list@mulberrytech.com'
> > Subject: MSXML and Namespaces ... not fully implemented (was RE: Has
> > docum ent(string) in MSXML 3 (July preview) worked for any one?)
> > Sensitivity: Private
> >
> >
> > Sara, folks,
> >
> > > -----Original Message-----
> > > From: sara.mitchell@ps.ge.com [mailto:sara.mitchell@ps.ge.com]
> > > Sent: Wednesday, September 06, 2000 6:51 PM
> > > To: Extern.Eckenberger@kmweg.de
> > > Subject: RE: Has document(string) in MSXML 3 (July preview)
> > worked for
> > > any one?
> > >
> > > Thanks! It confirms my suspicions which is that the problem
> > > is how MSXML is being invoked by the scripting engine. One
> > > question: did you run the transformation from a command
> > > line? or is it being done dynamically from a script|ASP|etc.?
> >
> > I just opened the document with a double click, so I guess
> > you can say I
> > used the commandline ... :-). However, looking at your problem I was
> > thinking that you might be using namespaces and as I just
> > came across a
> > problem with namespaces in one of my projects and I thought
> > that they might
> > be conneced.
> [snip]
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list