On Sunday 17 October 2010 7:15:33 pm Robert Liguori wrote: > Consider CXF's support of the following WS-* specifications: WS-Addressing, > WS-Policy, WS-RM, WS-Security, WS-SecurityPolicy, WS-SecureConversation > and WS-Trust (did I miss any?)... > > My question is: Is CXF compliant with usage of each WS-* implementation? > That question is a little awkward... maybe more like, "Is CXF using > compliant WS-* implementations and does CXF WS-* support-modules retain the > WS-* compliancy"? > > Case Study: I guess if we can say that Apache Neethi is compliant to > WS-Policy, which they do claim, then by CXF using Apache Neethi, is CXF > automatically compliant? Or is it possible that the module > (cxf-rf-ws-policy-2.3.0.jar) that CXF uses to bridge the technology would > need to be tested for compliancy as well?
Well, there aren't really test kits for most of the WS-* technologies like there are for things like"JAX-WS" and "JAX-RS". Thus, claiming compliance is really along the lines of "we're quite confident is works. If it doesn't, we'll get it fixed." That said, we do (have done) quite a bit of testing between CXF and other implementations to make sure it works. In particular, we've done quite a bit of testing with the MS InteropPlugFest things: http://mssoapinterop.org/ilab/ which cover a wide range of the WS-* technologies. > Note: Can someone tell me the source implementation of each WS-* technology > that CXF is using? For WS-Policy, it's semi-neethi. We only use part of Neethi (the model), but not the builders and such due to the Axiom requirements. For WS-Security relates stuff, the underlying library is WSS4J, but for the WS-SecPol, WS-SecConv, WS-Trust hooks, that's all part of CXF itself as part of it's cxf-rt-ws-security module. WS-Addressing and WS-RM are built into CXF. (cxf-rt-ws-addressing and cxf-rt- ws-rm modules) -- Daniel Kulp [email protected] http://dankulp.com/blog
