Saxon

I have deleted the attachment because it contained a Saxon license file. Please never post your license file in a public place.

When can I expect this to be resolved?

I also tried xsltTransformer.Run (without onClose) than call next action but getting same issue, I am not able to find afterUploadAction method in library. I can find Close, onClose but not afterUploadAction.

afterUploadAction is the name of a method in your code that you posted, it's the method that you invoke in your onClose() callback.

As an experiment, it might be worth setting Feature.ALLOW_MULTITHREADING to false (using Processor.SetProperty()), to ensure that the secondary result documents are written in the main thread. I would be interested if that affects things.

It looks like you're running on Windows, which I've always found to be very sensitive about making sure that files are properly closed before attempting to read them. It's certainly possible that there's a problem in this area, but we need to eliminate other more obvious things first.

Another user seems to be experiencing similar problems:

https://stackoverflow.com/questions/72468963/how-to-close-a-file-produced-via-xslresult-document-with-saxoncs-correctly

I have tried several things also above commented facing same issue but waiting for resolution so is there any possible solution or we have to hit and try?

For your information in .NET version afterUploadAction is not available.

I have put together an example VS 2022 project which indeed seems to reproduce the problem of the SO question when run on Windows:

Error on line 15 column 4 of sheet2.xsl:
  FODC0002  Exception thrown by URIResolver resolving `result1.xml` against
  `file:///C:/Users/marti/source/repos/SaxonCSResultNotClosedTest1/bin/Debug/net6.0/sheet2.xsl'
   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode
  mode, FileAccess access, FileShare share, FileOptions options)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode,
  FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode,
  FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode
  mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String
  path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions
  options, Int64 preallocationSize)
   at System.IO.File.OpenRead(String path)
   at Org.XmlResolver.Utils.UriUtils._getFileStream(String uri)
   at Org.XmlResolver.Utils.UriUtils.GetStream(String uri, Assembly asm)
   at Org.XmlResolver.Utils.UriUtils.GetStream(Uri uri)
   at Saxon.Callbacks.DirectResourceResolver.resolve(JJ_ResourceRequest request)
   at Saxon.Hej.lib.JJ_ResourceRequest.resolve(JJ_ResourceResolver[] resolvers)
   at Saxon.Hej.functions.DocumentFn.resolveURI(String href, String baseURI, String
  documentKey, XPathContext context)
: The process cannot access the file
  'C:\Users\marti\source\repos\SaxonCSResultNotClosedTest1\bin\Debug\net6.0\result1.xml'
  because it is being used by another process.

Saxon.Api.SaxonApiException
  HResult=0x80131500
  Message=Exception thrown by URIResolver resolving `result1.xml` against `file:///C:/Users/marti/source/repos/SaxonCSResultNotClosedTest1/bin/Debug/net6.0/sheet2.xsl': The process cannot access the file 'C:\Users\marti\source\repos\SaxonCSResultNotClosedTest1\bin\Debug\net6.0\result1.xml' because it is being used by another process.
  Source=SaxonCS
  StackTrace:
   at Saxon.Hej.s9api.XsltTransformer.transform()
   at Saxon.Api.XsltTransformer.Run(IDestination destination)
   at Program.<Main>$(String[] args) in C:\Users\marti\source\repos\SaxonCSResultNotClosedTest1\Program.cs:line 42

However, when run under Linux (WSL, Windows Linux Subsystem), it runs fine.

Example project is at https://github.com/martin-honnen/SaxonCSResultNotClosedTest1

Branch https://github.com/martin-honnen/SaxonCSResultNotClosedTest1/blob/ResultDocumentHandler/Program.cs does

transformer.ResultDocumentHandler = (href, baseUri) => { 
    var serializer = processor.NewSerializer();
    var fs = File.Open(new Uri(baseUri, href).LocalPath, FileMode.Create, FileAccess.Write);
    serializer.OutputStream = fs;
    serializer.OnClose(() => { fs.Close(); });
    return serializer;
};

which seems to work around the problem

The method Emitter.close() calls writer.close() only if the variable mustClose is true. In Saxon 11, it is never set to true. This applies to the Java code as much as to the C# code. (But failure to close a file tends to cause problems only on Windows).

The general principle is that Saxon should close a stream or writer if (and only if) Saxon created the stream or writer, typically because it was supplied with a file or URI. It shouldn't close a stream or writer that was supplied by the user.

The design changed in 11 so the Emitter is always supplied with a UnicodeWriter; the logic for constructing this (and therefore the knowledge of whether it needs to be closed) are in the new class ExpandedStreamResult.

The next part of the problem is specific to SaxonCS: the C# emulation of class StreamResult differs from the original in that the constructor supplying a File creates a FileOutputStream immediately, losing the information that the stream was system-constructed rather than user-constructed, and therefore needs to be closed by the system after use.

The patch described in comment 18 has now been applied to the 11.x branch, to go out with 11.6. See also bug #5886.