Closed BryceStevenWilley closed 1 year ago
CXF 4.0 is out, so this upgrade can start now: https://cxf.apache.org/docs/40-migration-guide.html.
Had to avoid this issue on CXF 4.0.0: https://stackoverflow.com/questions/72128029/how-do-i-resolve-could-not-find-artifact-javax-xml-bindjaxb-apipom2-3-0-b1611
An extremely internal issue with some java libraries. The main gist is that the whole "Java EE" is a brand name owned by Oracle, so in 2017, the Eclipse foundation was forced to change the package names to jakarta instead. http://blog.supol.cz/?p=202 is the best source I have found that explains the technical side of everything in detail.
This essentially means that we are using outdated versions of libraries, specifically the
javax.ws.rs-api
andjavax.jws-api
libraries. New development on those is onjakarta.ws.rs-api
andjakarta.jws-api
. However, we're still using the olderimport javax.*
statements pretty much everywhere, and notably,wsdl2java
still generates code using these statements. https://issues.apache.org/jira/browse/CXF-8371 is the tracking issue forwsdl2java
working with Jakarta E 9.0.