CXF Upgrade to latest | Community
Skip to main content
diana-raileanu
Level 2
March 28, 2025

CXF Upgrade to latest

  • March 28, 2025
  • 3 replies
  • 1014 views

Hi,

 

AEM 6.5 SP22

We are trying to upgrade CXF (3.3.5 is the current version) to 4.0.7 (latest version that support jdk 11). But once we upgrade the version, the bundles start to have dependencies issues. We've tried adding the compile dependencies both required and optional specified in https://mvnrepository.com/artifact/org.apache.cxf/cxf-core/4.0.7, but that still doesn't help - the cxf core bundle never resolve. The dependency list keep growing and there is no end to it. Is there any example with cxf usage for a more cent version that 3.3.5 that we have now? 
We need the solution to be compatible with the cloud as this is what we are aiming for. 

 

Thank you.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

kautuk_sahni
Community Manager
Community Manager
April 2, 2025

@estebanbustamante, @sarav_prakash, @narendiran_ravi, @dprakashraj, @asutosh_jena_, @rohan_garg, @daniel-strmecki Your expertise would be really valuable here! Please have a look at this question when you get a chance.

Kautuk Sahni
daniel-strmecki
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 2, 2025

Sorry, but its been a really long time since I used CXF. Back then, it also caused us many problems when upgrading AEM, so we decided not to use it anymore.

 

Good luck,

Daniel

diana-raileanu
Level 2
April 2, 2025

@daniel-strmecki can you please share what implementation did you switch to? We are not bound to CXF and if we can achieve the same using other client implementation, we would gladly change this.

Thank you in advance,

Diana

diana-raileanu
Level 2
July 16, 2025

@diana-raileanu Got it, but then maybe look at a more lightweight alternative, as CXF is quite a comprehensive library supporting more than just SOAP. It's been a long time since I worked with SOAP, so maybe I am wrong, but if I remember correctly, you just need to generate the client code to send/receive SOAP requests, not sure if you actually need to deploy a 3rd party library to AEM.

 

Good luck,

Daniel


@daniel-strmecki Yes, we considered that and even tried it out, the problem is the soap service in place (which we can't control or change) doesn't accept connections with a lightweight setup, it requires a (or similar)

JaxWsProxyFactoryBean

in order to establish the connection, and I couldn't find such proxy alternative from a more lightweight library.

kautuk_sahni
Community Manager
Community Manager
April 8, 2025

@diana-raileanu Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

Kautuk Sahni
diana-raileanu
Level 2
April 8, 2025

@kautuk_sahni unfortunately the suggestions didn't help solve my issue, so now I am trying to build a brand new client with latest jakarta dependencies and have that deployable in AEM. But even this is not yet finished. When I have that working I will post here the solution, and maybe even create a POC project in github, for other people who have to consume soap service.