Saxon 8.8. is coming out within a couple of weeks, and will have this
capability (though it still needs some further testing). I suggest you wait
till then. In principle you could get it working now by writing your code in
Java and using the IKVMC technology to cross-call to .NET and COM, but it's
probably easier to wait.
[mailto:saxon-help-bounces@...] On Behalf Of Steve Turner
Sent: 18 August 2006 22:08
Subject: [saxon] .NET Extensions in Saxon?
My apologies ahead of time if this is not the proper forum! This question
is kind of a mix :-).
I am pretty stuck here. I need to use a COM object to basically get some
information downloaded to a local machine (save in say "C:\Temp\mydata.txt)
and then link to it in the output html (href = "C:\Temp\mydata.txt"). I
took a preliminary look at Micrsoft's xslt processor, but got extremely
frustrated since what I am doing is modifying some complex, existing xsl
files written in xsl\xpath 2.0. Of course, Microsoft doesn't support 2.0,
and their "MVPs" get very defensive when one suggests that this is bogus.
So, I downloaded Saxon 8.7.3, which has some very nice .NET objects for
doing the transformations. Nice job. There is even a link in the help file
that suggests that writing extension functions in .NET might be possible.the
link is there, but the file dotnetextensions.htm is missing from the help
Finally, my question: can I write extensions in .NET in 8.7.3, or is there a
way that anyone knows of to (easily?) create a java package from a COM dll
that will run on the Sun 1.5 VM? I was something somewhere that indicated
this was possible, but the article was a bit stale (from 1999) and seemed to
imply that it would work only on Microsoft's VM.
Again, I am exceptionally new to xslt and saxon, so my apologies if this
forum is not correct.
Notice: This e-mail message, together with any attachments, contains
information of Symyx Technologies, Inc. or any of its affiliates or
subsidiaries that may be confidential, proprietary, copyrighted,
privileged and/or protected work product, and is meant solely for
the intended recipient. If you are not the intended recipient, and
have received this message in error, please contact the sender
immediately, permanently delete the original and any copies of this
email and any attachments thereto.