2022.12 (December 2022)

Update Required to the odeLoadBalancerFactory Bean

A typographical error has been corrected in the bean named odeLoadBalancerFactory that references class com.sas.finance.fraud.ol.monitor.OdesDynamicFailoverLoadbalancerFactory. Correct the bean argument periodeInSec to periodInSec.

<constructor-arg name="periodInSec" value="30"/>

Using Multiple Simple Expressions within a Dynamic Endpoint Definition

If you use two simple expressions within a dynamic endpoint definition, then an invalid endpoint is generated. Here is an example of two simple expressions:

<route>
   <toD 
uri
="https:$simple{exchangeProperty.testconfig[processphoto-api-base-url]}?userToken=$simple{exchangeProperty.X-   USERTOKEN}
&amp;
httpMethod=POST
&amp;
copyHeaders=false
&amp;
bridgeEndpoint=true"
/>
</route>

The above route generates an invalid endpoint by appending an additional HTTPS.

https://https:retailid-test.intellicheck.com/api/CamUploader/
ProcessPhoto?bridgeEndpoint=true©Headers=false&httpMethod=POST

If you need to use more than one simple expression within a dynamic endpoint definition, you should provide the solution within Groovy. In the following example, the query string userToken has been set like any of the other message headers.

<route>
   <toD 
uri
="https:$simple{exchangeProperty.intellicheckConfig[processphoto-api-base-url]}?httpMethod=POST
&amp;
copyHeaders=false
&amp;
bridgeEndpoint=true"
/>
</route>

Update Required to the removeHeader EIP

If you use the removeHeader EIP in the XML DSL files of your routes, then you need to change the headerName attribute to name.

Here is an example before migration:

<removeHeader headerName="Authorization"/>

Here is an example after migration:

<removeHeader name="Authorization"/>

For more information about the removeHeader EIP, see the Camel documentation.

If you licensed any of the following third-party adapters and use the adapter sample route code, all instances of the removeHeader EIP need to be updated to use the name attribute.

• Boku: routes/boku-route-test.xml (1 occurrence needs to be changed)
• Intellicheck: routes/intellicheck-route-test.xml (5 occurrences need to be changed)
• Iovation: routes/iovation-route-test.xml (2 occurrences need to be changed)
• Prove: routes/payfone-route-test.xml (2 occurrences need to be changed)

Changes Affected by a Jackson Library Upgrade

The Jackson library is upgraded. This version of the library requires JavaTimeModule when LocalDate types are used. This module gets automatically registered by Spring Boot when you add the jackson-datatype-jsr310 dependency as follows:

compile 
"com.fasterxml.jackson.datatype:jackson-datatype-jsr310:
$
{jacksonDatatypeJsrVersion
}
"

The following example shows a verbose representation of a date in JSON when you use an older version of Jackson:

"trgDate5":{"year":2022,"month":"AUGUST","era":"CE","dayOfYear":217,"dayOfWeek":"FRIDAY","leapYear":false,"dayOfMonth":5,"monthValue":8,"chronology":{"id":"ISO","calendarType":"iso8601"}}

However, with the new version of Jackson, the default date format is changed and LocalDate is now serialized as follows:

"trgDate5":"2020-12-24"

The above is the ISO standard format. However, with the custom data type converter you can still convert dates to the legacy format, if needed.

Legacy Mode Change

If you use SOAP in any of your configurations, you need to add additional JAR files. You can download these files from their respective maven repository and include them in the lib directory.

• javax.xml.soap-3.1.1.jar
• javax.xml.soap-api-1.4.0.jar
• saaj-api-1.3.5.jar
• saaj-impl-1.4.0.jar