axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raymond Domingo" <raym...@domingo.nl>
Subject No Deserializer found to deserialize a ':parameters' using encoding style 'null'
Date Mon, 01 May 2006 12:18:52 GMT
Hello  everyone,

We are STRUGGELING to connect our soap client to our axis server  for some
time now, PLEASE HELP !

We suspect there is a problem with the encodingStyle. We created a test client
 (using axis) and it works ok. After comparing the soap message (obtained
using sniffer) 
 from our Testclient and the soap client we discovered the soap client is
using an encodingStyle, and our working test client is not.  

There is also some difference in the namespace, 
but we assume this difference isn’t the cause. Because it should do exactly
the same. See snapshot of xml below:

The Exception from soap client:
2006-05-01 09:53:57,503 - ERROR - (nl.foo….) - Invoking 'adHocVragen' failed!
[SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to
deserialize a &apos;:parameters&apos; using encoding style &apos;null&apos;.;
targetException=java.lang.IllegalArgumentException: No Deserializer found to
deserialize a ':parameters' using encoding style 'null'.]
        at org.apache.soap.rpc.Call.invoke(Call.java:294)
…

Our testclient xml:
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope 
	xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
	xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
        <AdHocVragen xmlns="LRDServiceSOAP.xml">
            <parameters xmlns="">

Our soap client xml
<?xml version='1.0' encoding='utf-8'?>
<SOAP-ENV:Envelope 
	xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
	xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <SOAP-ENV:Body>
        <ns1:adHocVragen xmlns:ns1="LRDServiceSOAP.xml"
SOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml">
            <parameters>

We can’t change our client code, because it is already used by many customers. 
Currently we are building a new webservice using axis.
We are using axis 1.3 and soap 2.3.

Can anyone please explain to me why my soap client can’t connect to the axis
server ?

Best regards,
Raymond domingo


Mime
View raw message