Oskar Otw wrote:tried to make, with wsmiport, Client Side Skeleton without success
Peer Reynders wrote:
The WSDL uses the rpc/encoded messaging mode with SOAP encoding which is not supported by current generation SOAP stacks like JAX-WS, Axis2, or Apache CXF.
Oskar Otw wrote:Hmm, maybe i don't understand what i should do...
I have WS in webshop and I'm trying to get orders via SOAP. I'm sending request and getting error:
I need to write my own Deserializer or what? Thanks in advance for any clue.
Oskar Otw wrote:Hmm but like I said I had used wscompile.bat to generate code. Now i have planty of classes, and I want to connect with WS and get response, but when I'm trying simply code i need to implement all abstract methods, and i don't have any idea what should i put into them, my main.class:
The Java API for XML-Based Web Services (JAX-WS) 2.1 (JSR 224) maintenance release 2 specification wrote:
The following are non-goals:
SOAP Encoding Support Use of the SOAP encoding is essentially deprecated in the web services community, e.g., the WS-I Basic Profile excludes SOAP encoding. Instead, literal usage is preferred, either in the RPC or document style. SOAP 1.1 encoding is supported in JAX-RPC 1.0 and 1.1 but its support in JAX-WS 2.0 runs counter to the goal of delegation of data binding to JAXB. Therefore JAX-WS 2.0 will make support for SOAP 1.1 encoding optional and defer description of it to JAX-RPC 1.1. Support for the SOAP 1.2 Encoding is optional in SOAP 1.2 and JAX-WS 2.0 will not add support
for SOAP 1.2 encoding.