RE: Scripts with Saxon

Subject: RE: Scripts with Saxon
From: "Aaron Skonnard" <aarons@xxxxxxxxxxx>
Date: Fri, 30 Jun 2000 12:56:21 -0600
With MSXML 3.0, you don't actually need JavaScript. It let's you associate
COM objects with a namespace URI that can be leveraged throughout the
transformation like any extension. To do this, you need to add it to your
processor's context before calling transform as follows:

Set obj = CreateObject("mylib.myobject")
processor.addObject obj, "urn:mylib"

See the IXSLProcessor and IXSLTempalte interfaces for more details. If the
mylib.myobject component supports a method called 'method1()' and a property
called 'property1' you could use them as follows:

<xsl:transform version="1.0"
   <xsl:template match="/">
     method1 returns: <xsl:value-of select="mylib:method1()"/>
     property1 returns: <xsl:value-of select="mylib:get-property1()"/>


> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of Kay Michael
> Sent: Friday, June 30, 2000 3:27 AM
> To: 'xsl-list@xxxxxxxxxxxxxxxx'
> Subject: RE: Scripts with Saxon
> > With a little help (actually a lot) from this list
> > I have outputted the data to a file which is processed
> > afterwards with a C-program.
> >
> > Now I would like to know if it's possible to accomplish
> > this processing within a stylesheet.
> >
> > I've been told that this is possible with MSXML
> >   1 Is that true?
> >   2 Can it be done with Saxon?
> >
> Saxon allows you to call external functions written in Java
> (only). I think
> MSXML allows JScript and hence access to any external COM object.
> Mike Kay
>  XSL-List info and archive:

 XSL-List info and archive:

Current Thread