Skip to content

Conversation

stataru8
Copy link

@stataru8 stataru8 commented Sep 22, 2025

🏁 Context

🔍 What is the problem this PR is trying to solve?
Blueprint files cannot properly use the CXF Jetty xmlns because there is no handler. Currently, installed handler is for Spring.

🚀 What is the chosen solution to this problem?
Port a recent commit from the official camel-karaf repo where the CXF Jetty blueprint xmlns handler was re-added.
Set the Blueprint handler for CXF Jetty xmlns as the default one.

🎾 Impacts

  • This PR introduces a breaking change

Dear contributor, please check if the PR fulfills these requirements

  • The PR commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • Related design / discussions / pages (not in jira), if any, are all linked or available in the PR

@stataru8 stataru8 requested a review from a team as a code owner September 22, 2025 14:03
@stataru8 stataru8 changed the title fix(DPE-1805): Regression: re-add CXF Jetty xmlns handler in camel-karaf fix(DPE-1805): re-add CXF Jetty xmlns handler in camel-karaf Sep 22, 2025
Copy link

@f2par0 f2par0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@stataru8 stataru8 changed the title fix(DPE-1805): re-add CXF Jetty xmlns handler in camel-karaf fix(DPE-1805): re-add CXF Jetty blueprint xmlns handler in camel-karaf Sep 25, 2025
@stataru8 stataru8 closed this Oct 1, 2025
@stataru8 stataru8 reopened this Oct 1, 2025
@stataru8 stataru8 closed this Oct 1, 2025
@stataru8 stataru8 deleted the origin/stataru/fix/SUPPORT-5788 branch October 1, 2025 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants