Common JAXRPC error - unexpected element name

If you are using JAXRPC, there is an error message that may be hard to connect back to the root cause of the problem. The error message reads something like:
unexpected element name: expected=FileMetadata, actual={urn:FileUpload}FileMetadata.

There may be multiple causes for this error message. The first you want to look at is the flavor of XML schema advertized in the WSDL.

The default value for the elementFormDefault attribute is unqualified (see the w3c spec), which is what the error message above is trying to convey. In the schema section of your WSDL, make sure you can find the declaration: elementFormDefault="qualified"

Sometime, this get lost in the edits of the WSDL file, and many Web Services toolkits wont validate on the consumer side (Axis and .NET are among those). If you cannot alter the original WSDL, make a local copy that you can use to generate your artifacts, then contact the service provider so that they can make the change. The WS-I tools should be able to help you detect this kind of issues with minimal efforts.

Comments

Aashish Dalmia said…
Awesome suggestion. It worked. I just modified my schemas by adding "elementFormDefault="qualified" in tag and it worked.

You were right, the error was hard to relate with the solution of the problem especially with the error log that it gave. Anyways...

Thank you so much.
12:19
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