We have just released version 5.38.1. Here is a list of the changes that came with the release:
Features
-
Multiple gRPC servers can now be recorded at the same time, for example:
com.example.Service/method -> host1:port1 com.example.packageA.* -> host2:port2 com.example.packageB.* -> host3:port3
- Added support for Java object Serializable Proto messages sent over JMS connections e.g. RabbitMQ RPCs
- Added support for sending multiple types of request/response message (e.g. two different Java Proto request/response pairs) on a single request/response queue pair
- Added support for RabbitMQ contentType header
- Added PostgreSQL example connection to database-connections.json
- JSON request/response field data in mappings can now be externalized to/from MappingData.csv for an alternative way to edit field data across multiple mappings in a table format
- Tools UI menu with links to simple file editor and mapping field data externalization
Fixes
- JMS advanced request and response types are now retained in the UI form when starting/stopping recording
- Improved HTTP recording UI error message when there is a problem fetching recording status in the UI
- Increase HTTP recording UI status timeout to cope better with slow browser connections
- If there is a problem decoding a recorded JMS message, fall back on a raw bytes recording representation
- Mention which actual connection ids were present when a JMS connection id is not found
- Removed deprecated "matches script" option from the request body matcher dropdown (replaced by dedicated fields)
Changes
- Upgraded bundled JRE from 8u352 to 8u362
- When matching JMS requests, mappings for Java object Serializable requests now must have the bodyType specified
- The default UI HTTPS certificate user-interface-https.jks was renewed
No comments:
Post a Comment