A new maintenance release of the E2E BRIDGE has been released. With this edition of our E2E Developer Newsletter we inform you about the latest features and bug fixes of the E2E BRIDGE software components. As usual, you find all details in our release notes that are provided in our Online Documentation.
In our completely re-designed E2E Forum you have the opportunity to compare notes on E2E BRIDGE and to exchange experiences on everything around the topic of IT integration and EDI.
The questions posed by other E2E BRIDGE users in particular can often result in input helpful for your own integration project. In addition, discussions with other users and IT developers offer you an opportunity to benefit from their experiences.
This is the last release of E2E BRIDGE and RUNTIME for RedHat Enterprise Linux 5. Reason is end of production phase for RedHat Enterprise Linux 5 since March 31, 2017. Please upgrade to a newer RedHat version.
This is also the last release of E2E BRIDGE and RUNTIME for Oracle Solaris x86. Please migrate to Linux or Windows.
We hereby announce that the E2E REST Adapter and REST Service (see REST Adapter and REST Service) have now reached stable release status. As of this BRIDGE version we guaranty backwards compatibility.
Please note the following restrictions for this release, if you use REST service or REST adapter:
Please use matching BRIDGE, RUNTIME and BUILDER versions and re-compile your services if necessary.
ugly@parameter-name) to externalName and give a better name. So you do not have to escape the parameter every time you use it.
See REST Adapter Reference > <<RESTParameter>> for more details.
See Implementing REST Methods > Output: Header Parameter for more details.
See REST Adapter Error Handling for more details.
If certain path segment contains special characters you don’t want to be URL-encoded, use option isVerbatimPath. This option will make the compiler process the variables, but doesn’t touch the path otherwise. The modeler himself will be responsible for the path to be encoded correctly, trimmed, etc.
See REST Adapter Reference > <<REST>> for more details.
date=:aDateVariable/...together with option isVerbatimPath to access those REST resources.
You now can read and update Node.js service configurations via the BRIDGE API.