V1.4.137 - Real-time request/response message substitution implemented

This V1.4.137 release of Wilma is focusing on a brand new feature: real-time message substitution, meaning that the request or response message that would go through the proxy/stub can be altered, even replaced completely. The addressed issue is #67. See details on how to do the real-time message substitution here.

Further improvements:

• The name generation of the logged messages was changed. It is possible to add a prefix of every Wilma instance. You may set it by specifying a new Wilma property: wilma.instance.prefix. If it is empty, nothing changes, but when there is a value, that value will be added to the front of the logged messages. Also it is possible to add a custom postfix to the name, by using interceptors. See more details on this feature here
• The content structure of the logged messages was changed a bit, as the headers can be altered, now it explicitly shows what headers were removed and what headers were added/changed
• Buggy custom (plugged-in) interceptors may cause exceptions in Wilma resulting in dropping the specific request/response. Now it is fixed: Exception caused by the bad interceptor is logged, but no message lost
• It is now possible to configure the Wilma -> Wilma Message Search ActiveMQ communication properties (hostname and port) that opens the possibility of having numerous Wilma instance working with a single Wilma Message Search. Also it is possible to have Wilma instance and Wilma Message Search on different (virtual) machines

Service API is extended to handle the new Response Volatility settings (status/on/off). (Java: V1.4.137, .NET: V1.4.5853.30788)
In case you upgrade, Wilma jars and the wilma.conf.properties file should be updated.

As usual, the release is available as docker images too.