• Initial version of the RESTServer generalInvoiceResponseManagerServer450 is published
  An introduction/overview and detailed documentation can be found at API Documentation
   
• The version of generalInvoiceResponseManager450.dll was incremented, but only to sync with the generalInvoiceResponseManagerServer450 version.
   

• This is a feature update, that does allow to read and analyze XML infosets without the named namespace prefix 'invoice:'. The corresponding XSD qualifies each element with elementFormDefault='qualified', that make XML files without a named namespace schema in effect invalid. However, it seems that such files are produced and this feature update allows to successfully overcome this error.
   

• Update of the code part responsible for the QR code production and layout. This update became necessary due to standardization change published by the QR standardization body.
  The updated code now produces standard compliant QR invoices that becomes normative beginning mid of 2020
   
• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix occuring in rare cases when an interface error is signalled but the error message is returned empty in GetAbortInfo()
   

• Bug fix of the printing engine not showing certain print objects like Datamatrix/QR codes when running the COM dll under a service environment.
   
• Revised/optimised logging regarding the binding to the interface instance has been implemented. This change improves analysis in a massive multi-threaded environment.
   
• Revised error management (enhanced binding to the interface instance) suitable for a massive multi-threaded environment
   
• The processing of a XML file is done in two passes due to memory and performance considerations. Any Base64 attachments are extracted and saved separately beforehand the basis XML data are loaded into the DOM. When splitting up these Base64 files a bug occurring with very small attachments was fixed.
   

Please read the document "Changes from V4.40 to V4.50..." for an overview about the major changes

• This is a feature update, that does allow to read and analyze XML infosets without the named namespace prefix 'invoice:'. The corresponding XSD qualifies each element with elementFormDefault='qualified', that make XML files without a named namespace schema in effect invalid. However, it seems that such files are produced and this feature update allows to successfully overcome this error.
   

• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix occuring in rare cases when an interface error is signalled but the error message is returned empty in GetAbortInfo()
   

• Revised/optimised logging regarding the binding to the interface instance has been implemented. This change improves analysis in a massive multi-threaded environment.
   
• Revised error management (enhanced binding to the interface instance) suitable for a massive multi-threaded environment
   
• The processing of a XML file is done in two passes due to memory and performance considerations. Any Base64 attachments are extracted and saved separately beforehand the basis XML data are loaded into the DOM. When splitting up these Base64 files a bug occurring with very small attachments was fixed.
   

• A cleanup task for temporary files has been added. In fact, all files temporary generated
  are deleted once the main interface is shut down. However, there are situations where files
  are still locked at shutdown and thus are not deletable at that moment. As a remedy, the cleanup
  task is started periodically to check for files older than 5 days that are deleted eventually.
   
• The detection of signed and/or encrypted XML files was improved such that the security library is
  loaded and initialized on demand. This measure ensures a better performance while stabilizing
  security library usage

• Check and possibly transform XML infosets to UTF-8 prior to be loaded into the DOM.
  This safety measure became necessary as various XML response files are delivered
  to providers written in wrong codepages, mainly ACSII.
   

• The code for getting a proper working directory was improved by taking into account more than one
  possible location (AppDATA and TempPath)
   

• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix occuring in rare cases when an interface error is signalled but the error message is returned empty in GetAbortInfo()
   

• Revised/optimised logging regarding the binding to the interface instance has been implemented. This change improves analysis in a massive multi-threaded environment.
   
• Revised error management (enhanced binding to the interface instance) suitable for a massive multi-threaded environment
   
• The processing of a XML file is done in two passes due to memory and performance considerations. Any Base64 attachments are extracted and saved separately beforehand the basis XML data are loaded into the DOM. When splitting up these Base64 files a bug occurring with very small attachments was fixed.
   

• A cleanup task for temporary files has been added. In fact, all files temporary generated
  are deleted once the main interface is shut down. However, there are situations where files
  are still locked at shutdown and thus are not deletable at that moment. As a remedy, the cleanup
  task is started periodically to check for files older than 5 days that are deleted eventually.
   
• The detection of signed and/or encrypted XML files was improved such that the security library is
  loaded and initialized on demand. This measure ensures a better performance while stabilizing
  security library usage

• Check and possibly transform XML infosets to UTF-8 prior to be loaded into the DOM.
  This safety measure became necessary as various XML response files are delivered
  to providers written in wrong codepages, mainly ACSII.
   

• The code for getting a proper working directory was improved by taking into account more than one
  possible location (AppDATA and TempPath)