1. The exact text of the error message indicates that the server uses Axis, not 
Apache SOAP.  Axis has its own mail list at [EMAIL PROTECTED]

2. The error message is generated by the server and simply reported by your 
client.  It indicates that the server thinks it is getting an element with 
xsd:anyType, but it does not know what to do with such an element, 
specifically, how to create a corresponding Java object to hold the data.

3. You say "what the server is looking for is"; how do you know this?  It is 
hard to believe that the server is expecting anyType type qualifiers, given 
that it claims it does not know how to deserialize that.

4. I am not a SOAP::Lite expert.  Is there any way in your code to indicate 
that the arrays are xsd:string?

5. Have you used SOAP::Lite debugging or tcpTrace or proxyTrace or tcpdump 
(*nix) or Network Monitor (Win*) or <your tool of choice here> to determine 
exactly what you are sending?  This is an essential aspect of SOAP debugging.

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message ----- 
From: "Tom Drought" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, April 18, 2005 9:58 AM
Subject: Re: No deserializer for {http://www.w3.org/2001/XMLSchema}anyType


The data that I am sending to it does not reference a type, though, what the 
server is looking for is:

<otherParams xsi:type="soapenc:Array" soapenc:arrayType="xsd:anyType[5]" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>
 <item xsi:type="soapenc:Array" soapenc:arrayType="xsd:anyType[2]" 
xmlns:ns2="http://www.w3.org/2002/12/soap-encoding";>
  <item xsi:type="xsd:string">domain_name</item>
  <item xsi:type="xsd:string">tyfdwefgdytwed.weduhwe</item>
 </item>
 <item xsi:type="soapenc:Array" soapenc:arrayType="xsd:anyType[2]" 
xmlns:ns3="http://www.w3.org/2002/12/soap-encoding";>
  <item xsi:type="xsd:string">seller_id</item>
  <item xsi:type="xsd:string">1</item>
 </item>
</otherParams>

Here is my code:

my $otherparams = SOAP::Data->name('otherParams' => 
 \SOAP::Data->value(
  SOAP::Data->name("item" =>
   \SOAP::Data->value(
    SOAP::Data->type('string')->name('item' => 'domain_name'), #domain name
    SOAP::Data->type('string')->name('item' => 'xmltester.com') #domain name
   )
  ),
  SOAP::Data->name("item" =>
   \SOAP::Data->value(
    SOAP::Data->type('string')->name('item' => 'seller_id'), #????
    SOAP::Data->type('string')->name('item' => '0') #????
   )
 )
);

There is a corresponding wsdl file, though, the server admin hasn't loaded it 
yet. I placed a copy of it on my site and tried to refernce my copy with no 
luck. Don't know if that would even be helpful.

Thanks for the help,
Tom
  ----- Original Message ----- 
  From: mdonaghue 
  To: [email protected] ; 'Tom Drought' 
  Sent: Monday, April 18, 2005 3:39 PM
  Subject: RE: No deserializer for {http://www.w3.org/2001/XMLSchema}anyType


  Tom, 



  I'm just learning this stuff myself. I believe a bunch of standard types are 
supported for Soap, and therefore have deserializers available. Serialization 
is the process that reduces objects to transferable bits. Either your type 
isn't supported (what is "anyType?") or you're not pulling in the correct 
schema to support it. Since the message says soapEnv:server, the message is 
being issued from the server, but again that may be due to the nature of the 
data or schema references sent to it. 



  Regards,

  Mark






------------------------------------------------------------------------------

  From: Tom Drought [mailto:[EMAIL PROTECTED] 
  Sent: Monday, April 18, 2005 8:05 AM
  To: [email protected]
  Subject: No deserializer for {http://www.w3.org/2001/XMLSchema}anyType



  Help. I have a SOAP:Lite script that is receiving the following error message:



  soapenv:Server.userException org.xml.sax.SAXException: No deserializer for 
{http://www.w3.org/2001/XMLSchema}anyType

  Does anyone know what it means and how I might be able to fix it? Is it 
client side or server side?



  Thanks,

  Tom

Reply via email to