cxf | Apache CXF is an open source services framework | SOAP library

If you have to specify some other artifact as parent, then spring boot needs to be moved under dependencyManagement tag parallel to dependencies like this:

I tried this pom:

It appears as though the http status code of 301 (moved permanently) being returned by the web site is not handled on the Java side. As a workaround, you can add "127.0.0.1 cxf.apache.org" to the hosts file, or block internet access using the operating system firewall.

We finally got this working!

We created a value object to capture information about the file:

There is no official version of CXF supporting Jakarta EE 9, however you can use the Tomcat Migration Tool for Jakarta EE to replace the namespace in the CXF jar files and your source code.

This is the approach also chosen by TomEE (which uses CXF) for its 9.0 series, so it should be relatively safe.

Tomcat 10.0 itself integrates the migration tool and can convert your WAR file before deployment if you put it in the webapps-javaee folder.

For anyone who stumbles upon this question, here's how I resolved it.

Once I started playing with the CXF demo code, I was able to simplify it to just its bare minimum set of dependencies and configurations. From there I was able to sort out that it was a matter of a missing dependency in my project.

For starters, we use dropwizard for the server, and we have a dependency on dropwizard-jaxws which brings in the cxf dependencies. I found by whittling away all of the layers, that the demo app only works if cxf-rt-transports-http-jetty is in the list of dependencies.

The transitive dependencies that dropwizard-jaxws include are:

The class org.apache.catalina.connector.Connector is part of Tomcat. In order for your application to work correctly on external servlet containers, the embedded copy of Tomcat must not be on the classpath of the web application (i.e. in /WEB-INF/lib). You set it correctly by setting the scope of the spring-boot-starter-tomcat to provided.

However now you have a problem, because the CdPlaylistadapterApplication has Connector in one of its method signatures and Spring Boot fails while creating an instance of the CdPlaylistadapterApplication class.

To solve it you need to move Tomcat specific configuration to another class (even nested) and protect it with the @ConditionalOnClass annotation:

Finally I managed to work this out. I am posting it here to help anyone else that could have the same problem.

It seemed to be related to the adapters created in Production during the deploy process (located in PASOEContent\WEB-INF\adapters\rest). When I did this deploy, I probably included a business entity for table "extcli", which was not in the project anymore. So, I undeployed the application and deployed again with a new generated .war file from Developer Studio. This new file didn´t reference to a adapters that doesn´t exist, and that seemed to be enough.

I am not familiar with Apache CXF, but based on CXF docs and the sample project I think I got it to work.

I downloaded a new Vaadin 14/Java 8 project from start.vaadin.com, and did the following:

1. Added the dependency