As it seems for some strange reason in CXF the oasp4j-starter-cxf-server-rest only works if additionally the dependency cxf-rt-ws-policy is present.
This is silly and seems like a design bug in CXF as REST should not depend on ws-policy what is SOAP related. However with only oasp4j-starter-cxf-server-rest in place the app wont boot up unless cxf-rt-ws-policy is present.
As oasp4j-starter-cxf-server-ws is indirectly depending on cxf-rt-ws-policy all works fine if both oasp4j-starter-cxf-server-rest and oasp4j-starter-cxf-server-ws are in place.
However, IMHO the idea of our Opt-In strategy should be that each starter works self-contained what is currently not the case.
Even though it appears odd, we IMHO need to add a dependency to cxf-rt-ws-policy in oasp4j-starter-cxf-server-rest.
As it seems for some strange reason in CXF the
oasp4j-starter-cxf-server-restonly works if additionally the dependencycxf-rt-ws-policyis present. This is silly and seems like a design bug in CXF as REST should not depend on ws-policy what is SOAP related. However with onlyoasp4j-starter-cxf-server-restin place the app wont boot up unlesscxf-rt-ws-policyis present. Asoasp4j-starter-cxf-server-wsis indirectly depending oncxf-rt-ws-policyall works fine if bothoasp4j-starter-cxf-server-restandoasp4j-starter-cxf-server-wsare in place. However, IMHO the idea of our Opt-In strategy should be that each starter works self-contained what is currently not the case. Even though it appears odd, we IMHO need to add a dependency tocxf-rt-ws-policyinoasp4j-starter-cxf-server-rest.