SAP and the SAP Integration Suite team are constantly looking into ways to improve the product quality and service to our customers.
As a part of continuous improvement, SAP Cloud Integration on SAP BTP Neo Environment is upgrading its Apache Camel Version from 2.x series to 3.x series.
In the latest Apache Camel version, Apache Camel has modularized its core and therefore several Apache Camel packages are either moved to different Camel package structure or completely removed. There are several breaking and incompatible changes.
We have noticed that you use one of the following Groovy Script/JavaScript in your integration flows:
“org.apache.camel.Attachment"
"org.apache.camel.impl.DefaultAttachment"
The above mentioned Camel Package/Classes have been moved by Apache Camel in version 3.x, thus execution of the impacted Groovy Script/JavaScript will lead to a compilation failure and eventually failure of processing of the integration flow.
From SAP, we will be providing a Wrapper - AttachementWrapper, by consuming which the impacted Groovy Scripts/JavaScript will not face a compilation error with respect to the above mentioned packages.
Please note that the usage of AttachementWrapper is compatible with both 2.x and 3.x, therefore you are advised to make the necessary changes as soon as possible.
Post #212
1.41K
- 👍 19