Apama 10.7.2 | Release Notes | What's New In Apama 10.7.1 | Miscellaneous changes in 10.7.1 affecting backwards compatibility
 
Miscellaneous changes in 10.7.1 affecting backwards compatibility
The following changes in Apama 10.7.1 affect backwards compatibility to previous Apama versions:
*While sending a request, the HTTP client transport no longer sets a content-type header from metadata.contentType if the body is empty. If you want to send the content-type even if the body is empty, you now have to set metadata.http.headers.content-type explicitly in the request. See also Handling HTTP headers.
*The YAML file that was provided with the HTTP client's generic JSON transport for using predefined generic event definitions is now used as a linked resource. Therefore, the bundle instance file HTTP_Client_bundle_instance.yaml is no longer created for the generic option (see also Adding the HTTP client connectivity plug-in to a project). To work with the newer version of this bundle, you have to call the engine_deploy tool again on your project.
Existing bundle instances for the generic option will be discarded. In case you modified the bundle and still want to use it, the chain definition name must be explicitly mentioned when creating a transport:
HttpTransport.getOrCreateWithConfigurations(host, port, {HttpTransport.CONFIG_DYNAMIC_CHAIN_DEF_NAME: "modified-chain-definition-name"});
Also, the chain name has been changed from HTTPClientGenericChain to HTTPClientGenericJSONChain. If you are using this chain, you have to update any EPL where you refer to HTTPClientGenericChain in the chainDefnName argument of a createDynamicChain() call to reflect the changed behavior. See also Creating dynamic chains from EPL.