After Camel migration, CamelXsltError is not being delivered to Camel exchange anymore

Solution Verified - Updated -

Issue

  • In camel 2.21.x (Fuse 7.5), when a transformation was attempted with xslt-saxon, an exchange property named ${exchangeProperty.CamelXsltError} was filled on the exchange, if any errors happened during the process.
  • This property has disappeared from the Exchange, although it is still documented for the xslt-saxon component. The error info is not seen in any other header or property with the info either.

Environment

  • Migration from Camel 2.x to Camel 4.x
  • Saxon library upgraded from 9.8 to 12.3 HE

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content