Saxon

Legacy ID: #2923220 Legacy Poster: Michael Kay (mhkay)

I depends on x! You'll need to look up the details for the particular version you are using. Information for all versions is here on the SourceForge site. I'd suggest however that you try and keep up with the latest versions: the current one is 8.2. The further you get behind, the harder the transition eventually becomes; and I don't investigate problems unless they can be reproduced on the latest version. Michael Kay

Legacy ID: #2923243 Legacy Poster: mbeaty (mbeaty)

Michael, Thanks for the reply. I did find the documentation. It appears 7.9.1 only requires Jaxp 1.2, which is what I was looking for. Here's my problem in a nutshell. I am doing some XSLT via an extension to a third-party proprietary app (Vignette Content Management System). My stylesheet needs to use something equivalent to the saxon:parse extension function. However, I'm finding it difficult to use Saxon with this 3rd-party app, since they seem to be quite dependent on Xalan and I don't really seem to have much control over swapping in a different transformer. Do you know of any equivalent function to saxon:parse in Xalan which I can use, or another way of doing the same thing? I'm stumped. Thanks. MB

Legacy ID: #2923394 Legacy Poster: Michael Kay (mhkay)

Sorry, but the free support service doesn't extend to competitor's products... I can offer some help if you have a budget to pay for it. Michael Kay

Legacy ID: #2923512 Legacy Poster: mbeaty (mbeaty)

Ok, so does anyone out there know a Xalan alternative to the saxon:parse extension. -MB