The 8.5/.../12.2 version of Connector for Web Services contains the following fixes:

build 12.2.9.0009
-----------------
Infor Reporting: Printing of subreports fails when using "Amazon Corretto" Java.

build 12.2.8.1961
-----------------
Large response messages will be reported in the log file. (Default threshold is 250 MB.)

build 12.2.8.1924
-----------------
Limit the waiting time for initialization of bshell to 5 minutes.

build 12.2.6.1854
-----------------
Fixed the problem that activation type "none" could not be used.

build 12.2.6.1844
-----------------
Infor Reporting: Sometimes a wrong barcode was printed (if two different barcodes had the same "hash" value).
MT Cloud: Metrics are collected about connection pooling and performance of SOAP/IMS requests.

build 12.2.3.1737
-----------------
Automatic reload of settings (c4wsProperties.xml) will not happen if timestamp of file
is older than the previous one.

build 12.2.2.1674
-----------------
Support for ION Messaging Service (IMS) v2 requests. ("multipartMessage" used
for BOD publishing to LN.) 
Note: version numbers are now following the LN UI numbering (12.2.2.x) instead
of the Enterprise Server numbering (10.7.1.x).

build 10.7.0.0079
-----------------
Support for ION Messaging Service (IMS) requests (used for "data lake publishing").
Some minor security-related fixes, required to obtain Veracode Level 4.

build 10.6.0.0064
-----------------
Infor Reporting: Improved performance when writing data files to the "Temporary Directory" network share.

build 10.6.0.0063
-----------------
Infor Reporting: Fixed problem with non-ASCII characters in function calls to tt_getLabel, tt_getText,
and tt_getMessage.

build 10.6.0.0057
-----------------
The JCA library uses a longer timeout value when starting-up a new bshell connection. This should prevent
timeout errors for slow LN systems.
Network problems during startup should no longer cause a deadlock ("hanging Tomcat").

build 10.6.0.0054
-----------------
The configuration folder for C4WS can now also be configured by supplying a JNDI Environment Entry
("configLocation = /path/to/configFolder")

build 10.6.0.0053
-----------------
Some libraries for XML processing were replaced to solve problems on IBM Java 1.8.0
The configuration folder for C4WS can now also be configured by supplying a Java system property
("com.infor.c4ws.configLocation = /path/to/configFolder")

build 10.6.0.0052
-----------------
The OAuth 1.a validation now also accepts signatures made with HMAC-SHA256 (in addition to HMAC-SHA1).

build 10.5.1.0042
-----------------
Basic Authentication in HTTP header can be used to pass LN credentials.
Tenant ID "infor" is interpreted as "no tenant" and will not be passed to LN.
Client language and locale can be passed in HTTP headers.

build 10.5.1.0038
-----------------
"ERP Server" settings in "connectionpoints.xml" (as used in versions prior to 10.5.1) are automatically
converted to new-style configuration settings in "c4wsProperties.xml".

build 10.5.1.0029
-----------------
The 10.5.1 release supports "baanlogin_ssl" activation in combination with OAuth 1.0a authentication.
This is intended for the multi-tenant Cloud environment, but can also be used for on-premise environments
with ION-API.

build 10.5.0.0095
-----------------
BOI execution in C4WS can be altered to behave more like the BOI execution in Infor Integration
(via tmboaserver). If the BOI has been deployed with the option "Ignore BOI Metadata", then no
default values will be added for "required" fields that are not present in the request. (Effectively,
all fields are treated as "optional".) This option was added because the BOI Domain Pack incorrectly
defines many optional fields as "required".

build 10.4.2.0084
-----------------
Automatic refresh of "Status" page of C4WS can be disabled (by clicking a link on the page).
JCA now has a new setting "Max Threads" which enables queueing of requests. This setting can
be specified in the "ERP Server" admin page.

build 10.3.0.0060
-----------------
Support for "generic" SOAP requests: SOAP requests that do not conform to the WSDL that belongs to the
deployed BDE (but to a similar, externally defined WSDL) can be processed if a suitable XSL file has been
placed in WEB-INF/wsdl. The XML transformation specified in the XSL file is responsible for converting
the generic request into an LN request, and converting the resulting LN response into a generic response.

build 10.3.0.0059
-----------------
Anonymous requests (requests without overriding credentials in the SOAP header) can now be blocked.
This is configurable on the "ERP Servers" admin page.

build 10.2.1.0054
-----------------
Multi-tenant environments can now be targeted by providing a query parameter ("tenant=...") on the request URL.

build 8.7.0.0050
----------------
Fixed concurrency issue with closing connections. In some situations a closed connection appeared in the idle pool, causing
a resource exception when it was reused.

build 8.7.0.0047
----------------
Fixed conversion from BDE exception to Fault response message.

build 8.7.0.0042
----------------
Increase connection timeout from 20 to 40 seconds.

build 8.7.0.0040
----------------
Increase version number to 8.7.0 (build 8.7.0.0040 is equal to build 8.6.0.0038)

build 8.6.0.0038 (published with solution <sol_nr>247624</sol_nr>)
----------------
- Keep alive timer does not work when BdeManager crashes.
- Keep internal admin up to date after crashing BdeManager or bshell.
- No longer use invalid connections (to crashed bshells) from the connection pool. 

build 8.6.0.0037 (published with solution <sol_nr>247120</sol_nr>)
----------------
- Enable configuration of Max references = 0.
- Support for rolling file logger (by specifying the maximum log file size and number of backups).
- Allow configuration change on running web server (can update ERP servers while SOAP requests are pending).

build 8.6.0.0034 (published with solution <sol_nr>246518</sol_nr>)
----------------
- Improvements for BOI support in C4WS: now supports associations and fills in default values.
- Better support for standards, can use xalan from other implementations.
- Upgrade external jars to latest versions.

build 8.6.0.0031 (published with solution <sol_nr>244036</sol_nr>)
----------------
Using Connector for Web Services (C4WS) with BOI web services may fail with NullPointerExceptions in the logfile.
This has been fixed in the JCA component of C4WS.

build 8.6.0.0028 (to be published with ESE 8.6)
----------------
New Infor Logo in C4WS screens.

build 8.6.0.0025 (to be published with ESE 8.6)
----------------
Set version number to 8.6, Using soap header, Support for dynamic setting of username/password and or company number 

build 8.5.0.0023 (published with solution <sol_nr>240179</sol_nr>)
----------------
Solution for defect TECH-00000-05404
Many BaanIV BOIs with layouts of type association do not work correctly as a WebService from c4ws.

Better default for iterator size to improve the performance.

build 8.5.0.0021 (published with solution <sol_nr>239849</sol_nr>)
----------------
Solution for defect TECH-00000-05392
When BDEs with the same name of different servers are being deployed, an additional suffix is added to the 
webservice name to be able to discriminate between the servers, which is correct.
HOWEVER, the WSDL code of these webservices include the same address location:
of the server from the last deployed BDE. This is incorrect.

Solution for defect TECH-00000-05356
When custom BOI's manager name does not end with xxxManager.class, Connector for Web Service does
not deployee this BOI.

build 8.5.0.0020
----------------
Solution for defect TECH-00000-05341
OutOfMemoryError when sending large xml documents with C4WS. Improved the iterator implementation
to consume less memory.

build 8.5.0.0017 (published with solution <sol_nr>237692</sol_nr>)
----------------
Solution for defect TECH-00000-05043
It is not possible to deploy one BDE in more than one ERP LN Server in Connector for WebService.
The WS is overwriting the existing service name and accordingly the address to access to the
service from external application. With this solution you will get unique service names for the
same service on different ERP servers.

build 8.5.0.0015 (published with solution <sol_nr>237345</sol_nr>)
----------------
Solution for defect TECH-00000-05026
Some custom BOIs cannot be deployed in c4ws. It results in a StackOverflowException.
This has been fixed in the WSDL generator.

build 8.5.0.0014
----------------
Solution for defect TECH-00000-05033
The response SOAP message is invalid because it contains xmlns:xmlns:xsi attribute.
This has been fixed.

build 8.5.0.0013
----------------
When using connector for webservices (c4ws) some errors are not reported as exception.
Improved the exception handling of BOI calls over the JCA transport.

