X4 Adapters: Bug fixes 7.5.0

X4BUG-310

Process Starter: When calling a process that does not exist or is incorrectly named, a successful status code including PUID was previously returned during asynchronous execution, while a non-specific error occurred during synchronous execution. This bug is now fixed and a unique error status and corresponding error message will occur while maintaining backward compatibility if the process specified in the Process parameter is not found.

X4BUG-312

Parallel Process Starter: Previously, non-existent or incorrectly specified processes always returned status code 1, regardless of whether the process was miswritten or a wrong protocol was used. This bug is now fixed and a unique error message with the status -1 is now generated if the process specified in the X4ProcessUrl parameter is not found.

X4BUG-1349

JSON Converter 2.0: The XML2JSON operation resulted in incorrect character encoding if the encodingType parameter was not explicitly set. This bug is now fixed and UTF-8 is used by default, even if encodingType is not specified.

X4BUG-1543

XML Element Wrapper: When merging two XML files with encoding="UTF-8", the output file was incorrectly created with encoding="Windows-1252". This bug is now fixed and the output file retains the original UTF-8 encoding.

X4BUG-1684

CSV Reader/CSV URL Reader: Fixed an issue where file streams did not close properly after scanning. The CSV adapters now release occupied memory immediately after the read operation is completed.

X4BUG-1686

The Microsoft Excel Reader encountered an error reading very large Excel files and the scanned file was not converted to an XML document. This bug is now fixed.

X4BUG-1856

Native adapters: When exporting a native adapter project via Package as Adapter, the operation failed if another native adapter was embedded that was not available in the repository but was integrated as a .jar file or WildFly module. In this case, the exception adapter description missing occurred. This bug is now fixed.