Invalid WSDL - and the answer is ...

I forgot to provide the answer on last quizz about invalid WSDL, and XML tips.

The WSDL in question: http://www.rajkovic.org/ws/wsdl/bads/annotatedBank2.wsdl

The issue: by mistake, I did reuse the same prefix for two namespace. The tns prefix is associated with 'http://ws.rajkovic.org/demo/annotatedBank'
at the global scope (wsdl:definitions) and reused with 'http://ws.rajkovic.org/demo/annotatedBank/types'
at the schema scope (xsd:schema element).

In the wsdl:part, element="tns:create-account" references an element named {http://ws.rajkovic.org/demo/annotatedBank}create-account, which is not found. Based on the schema's targetNamespace, the QName (qualified name) of the element is {http://ws.rajkovic.org/demo/annotatedBank/types}create-account.

There are two ways to fix this error:
  1. Uses the same targetNamespace URI (and tns prefix) for both WSDL and Schema elements. Keep It Simple as much as possible.
  2. Introduce a new prefixe in your wsdl:definition element (xmlns:types="http://ws.rajkovic.org/demo/annotatedBank/types") and uses the newly introduced prefixe to reference elements defined in your schema (element="types:create-account"). It's not a bad idea to avoid reusing the same prefix with different URI in a single document. That way, you will avoid this pitfall.
Remember: Keep It Simple, Stupid.

Here is today's WSDL: http://www.rajkovic.org/ws/wsdl/bads/kiss-20070104.wsdl. Can you spot the mistake?

I agree, it's getting a little more involved.

Have fun,

You can always get back to your favorite sudoku du jour.

Comments

Gerard Davison said…
Hi,

Although JDeveloper will happily generate me a webservice based on this document; but I think that the messgae part should reference a "element" rather than a "type" in the case of document/literal.

The WS-I analyzer would pick up this issue. Might be worth raising a bug so we can flag this in the code editor.

Gerard
02:54
Eric said…
Gerard,

You got this one right. I'll have to try using WS-I tool and see what error message we do get.

I'll have to see what we get on the server side with top-down assemble.

More next week...

Ecco
22:53
Post a Comment

Popular posts from this blog

Changing the version of JDK used by JDeveloper

I have recently learned a quick and lazy way to change the version of the JDK used to run JDeveloper 10g R3. I am sure there is an option somewhere in the configuration screen to do the same, which I couldn't find... While JDeveloper is not running, locate the embedded JDK on disk and rename (or delete) that directory. For me, it was C:\opt\jdev\jdk. Once it's done, restart and you will by asked to locate the version of the JDK you want to use. It's another step to get going with JAVA on Vista. -ecco
Read more

Connection reset from a WCF Web Service

Here is an error message you may see, when calling WCF Web Services from java: IOException retrieving the response: java.net.SocketException: Connection reset As it may not be obvious the first time you see it, this may save you some time. One reason for this behaviour is when the WCF endpint is expecting to see wsa:Action SOAP header in the request. To find out if you are facing this case, you have to look inside the WSDL, and search for the policy that describes the contract for your endpoint. <wsp:Policy wsu:Id="CustomBinding_Echo1_policy">   <wsp:ExactlyOne>     <wsp:All>       <wsaw:UsingAddressing/>     </wsp:All>   </wsp:ExactlyOne> </wsp:Policy> To make this a concrete example, here is a sample WSDL . To find the policy, you will need to follow the import as the policy are not always advertized in the top-level document. Here is how the import looks:   <wsdl:import namespace="http://example.org/" location="h
Read more

unexpected null value for literal data

There is a challenge that is hard to overcome at first; making sense of error messages. You can always Google with the text of the error, “unexpected null value for literal data” and hope to be lucky . If you are using Oracle Application Server 10.1.3.0, here is the explaination for the message and two ways out. The Exception: unexpected null value for literal data at oracle.j2ee.ws.common.util.exception.JAXRPCExceptionBase.<init>(JAXRPCExceptionBase.java:52) at oracle.j2ee.ws.common.encoding.SerializationException.<init>(SerializationException.java:26) ... The relevant schema: <complexType name="Customer"> <sequence> <element name="address" type="tns:Address"/> <element name="firstName" type="string"/> <element name="lastName" type="string"/> </sequence> </complexType> A sample code that will cause this exception: public void testServ() throw
Read more