| Author |
JAX issue - casting problem?
|
sonusgr sonusgre
Greenhorn
Joined: Dec 18, 2009
Posts: 1
|
|
Hi there,
I've got an odd issue with an externally provided WSDL. While feeding it to wsimport I get the following
[WARNING] not a WS-I BP1.1 compliant SOAP port "TestSoap": the wsdl binding has mixed style, it must be rpc-literal or document-literal operation!
line 471 of http://test.xxxxx.xx:8080/ITestService.asmx?WSDL
[WARNING] SOAP port "TestSoap12": uses a non-standard SOAP 1.2 binding.
line 474 of http://test.xxxx.xx:8080/TestService.asmx?WSDL
[WARNING] not a WS-I BP1.1 compliant SOAP port "TestSoap12": the wsdl binding has mixed style, it must be rpc-literal or document-literal operation!
line 474 of http://test.xxxxx.xx:8080/TestService.asmx?WSDL
generating code...
[ERROR] com.sun.tools.ws.processor.model.jaxb.RpcLitMember cannot be cast to com.sun.tools.ws.processor.model.jaxb.JAXBType
When loading the WSDL into SoapUI it all looks fine..is this a WSDL messup or a wsimport bug?
Thanks!
|
 |
Ivan Krizsan
Bartender
Joined: Oct 04, 2006
Posts: 2194
|
|
Hi!
My guess is that your WSDL has problems, given the error messages.
As stated, allowed binding styles are Document/Literal and RPC/Literal. This information is found in the <binding> element of the WSDL, as in this example:
Best wishes!
|
 |
sonusgr sonusgr
Greenhorn
Joined: Apr 10, 2006
Posts: 4
|
|
Hi Ivan, thanks for your quick reply!
The weird thing is that it works fine with Axis, but it fails with jax-ws (which is really what we need to work with)
I am posting an extract from the wsdl, if could spot anything that I cannot I ll be really grateful!
|
 |
Ivan Krizsan
Bartender
Joined: Oct 04, 2006
Posts: 2194
|
|
Hi!
Which are the lines that you get warnings about in the WSDL?
Since you post an extract, it is difficult to tell using the line numbers.
Best wishes!
|
 |
 |
|
|
subject: JAX issue - casting problem?
|
|
|