Refactor tests and QuarkusCxfProcessor #499
Conversation
and also in native mode * Put Woodstox stuff into a separate module so that Camel Quarkus can reuse it * Put jakarta.xml.ws related build steps into a separate WsApiProcessor so that there is some structure in the processors
…parate SaajImplProcessor class
…entations already available in io.quarkiverse.cxf.deployment.WsApiProcessor.registerForReflection()
…stead of abstract classes, fix related issues
…he dedicated method
ppalaga
force-pushed
the
220817-refactor
branch
from
c5b4a37 to
d5741aa
Compare
Bumps [woodstox-core](https://github.com/FasterXML/woodstox) from 6.2.7 to 6.3.1. - [Release notes](https://github.com/FasterXML/woodstox/releases) - [Commits](FasterXML/woodstox@woodstox-core-6.2.7...woodstox-core-6.3.1) --- updated-dependencies: - dependency-name: com.fasterxml.woodstox:woodstox-core dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
ppalaga
force-pushed
the
220817-refactor
branch
from
bb15063 to
fc57f93
Compare
|
Would anybody like to review? |
|
I can review in a couple hours. |
There was a problem hiding this comment.
LGTM @ppalaga ... one minor comment is that CXF 3.5.3 depends on woodstox-core 6.2.8. I'm not sure if switching that to 6.3.1 may have any unintended side effects?
Woodstox folks care for their backwards compatibility. Citing from their release page
So going to a newer minor should not be a problem. Also, if our tests pass it should be fine. |
No description provided.