Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Aggregate]XML declaration in CDATA part is removed by aggregation #337

Closed
Hooghof opened this issue Dec 20, 2024 · 0 comments · Fixed by #338 or assimbly/custom-components#137
Closed
Assignees
Labels
accepted bug Something isn't working support (Jira)
Milestone

Comments

@Hooghof
Copy link

Hooghof commented Dec 20, 2024

An aggregation of a message body that contains a CDATA section containing an xml declaration proceeds differently than in Camel2. An xml declaration must first be added to the body so that the aggregation component understands that it is an xml body.

On acceptance and on development there are identical testcases in the flow called aggregateXmlCdata (tenant Regression Tests). The test contains 3 routes:

  1. Without xml declaration and without Content-Type text/xml
  2. Without xml declaration but with Content-Type text/xml
  3. With xml declaration

On acceptance, the 3 test cases have the same output.
On development, only test case 3 gives the expected output.

https://dovetailworld.atlassian.net/browse/DOV-2173

@Hooghof Hooghof added the bug Something isn't working label Dec 20, 2024
@Hooghof Hooghof changed the title [Aggregate][Split]XML declaration in CDATA part is removed by aggregation [Aggregate]XML declaration in CDATA part is removed by aggregation Dec 30, 2024
@brunovg brunovg self-assigned this Jan 7, 2025
@brunovg brunovg added this to the 5.0.2 milestone Jan 7, 2025
@Hooghof Hooghof closed this as completed Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment