Saxon

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

I'm afraid at the moment there's nothing in the .NET API that allows you to direct the output of xsl:result-document anywhere other than a file. In fact, there aren't any callbacks in the interface at the moment (there's no CollectionURIResolver or CollationResolver for example). I did this deliberately at the time because I wanted to keep the interface as simple as possible and avoid making rash decisions, and also because implementing callbacks between Java and .NET is another little bit of technology that needs to be mastered; but it does need to be done and I'll keep it in mind. Michael Kay

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

Having said that, if you're feeling ambitious you could try and implement something based on the underlying Java API. If you want to try and tackle that I'll offer what help I can. It will mean understanding the IKVMC cross-compilation technology.

Legacy ID: #4133576 Legacy Poster: mjp (mperestrello)

Hi Michael, Thanks for your prompt reply. I have two other issues to solve in my project and then I would be glad to attempt the callback implementation. I'll be available in around two weeks time, do you have any pointers (written one's !) to get me on the right track. Regards, Marco

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

I found a spare moment to implement this feature, so it will appear in the next Saxon release. It turned out to be no problem writing a C# class to implement a Java interface, which is what had been holding me back. Michael Kay

Legacy ID: #4140768 Legacy Poster: mjp (mperestrello)

Thank you for the effort, I look forward to the new release.