Spring WS is JAX-WS compliant
Is Spring WS JAX-WS compliant? To be more complicated
- Does Spring-WS provide functionality according to JAX-WS standards?
- Does Spring-WS support all features specified in JAX-WS?
Background on the question: We are trying to develop several web services. Before starting these projects, we want to develop a standard web service structure. So we want to stick with one WS implementation, either Spring WS or JAX-WS. Based on research, I learned a lot of details about their implementation (see below). Even though the Spring WS project does not officially mention that it follows JAX-WS, I want to know if it continues to complain about the JAX-WS standards.
Some well-known facts:
"Spring only supports the first WSDL contract for code" VS "JAX-WS provides as code-WSDL, WSDL code"
"In Spring WS, an incoming request is handled at the XML message request layer (flexibility)" VS "An incoming request is handled as method calls."
Spring WS Standards ( link )
- SOAP 1.1 and 1.2
- WSDL 1.1 and 2.0 (XSD-based generation is only supported for WSDL 1.1)
- WS-I Basic Profile 1.0, 1.1, 1.2 and 2.0
- WS-Addressing 1.0 and draft in August 2004
- SOAP Message Security 1.1, User Token Profile 1.1, X.509 Certificate Token Profile 1.1, SAML Token Profile 1.1, Kerberos 1.1 Token Profile, Basic Security Profile 1.1
JAX-WS RI standards supported ( link )
- JAX-WS 2.0 / 2.1 / 2.2 (JSR 224)
- WS-I Basic Profile 1.2 and 2.0
- WS-I Attachments Profile 1.0
- WS-I Simple SOAP Binding Profile 1.0
- WS-Addressing 1.0 - Core, SOAP Binding, WSDL Binding
From the above details, it can be said that SOAP WS does not support JAX-WS 2.0 / 1/2 standards. However, I want to officially learn from the Spring-WS team that the JAX-WS standard is compliant? Please let me know if my question should be designed with a specific purpose or purpose.
source to share
No one has answered this question yet
Check out similar questions: