Tom,

 

It looks like it’s being serialzed into an array of otherParams, which in turn contains two arrays of consisting of two items apiece.  The arrays are what are being converted to “anyType”. So, the serialization process is assigning the anyType value because of what it thinks is an (implicit) array.  It’s assigning the type of anyType[5] to the first and anyType[2] to the intererior.

 

Your tree looks like this:

 

Value

            Name

                        Value

                        Value

            Name

                        Value

                        Value

 

But the only value type you’re explicityly assigning is the lowest level values. Check out what happens when you specifically assign a type to the Outer value (Array?) and the Name values (Array?)

 

Also, should it be an array at all? If were a standard tree, wouldn’t its level in the hierarchy eliminated the need for an array declaration?

 

Regards,

Mark

 

 

 


From: Tom Drought [mailto:[EMAIL PROTECTED]
Sent: Monday, April 18, 2005 9:58 AM
To: [email protected]
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.xmlsoaporg/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

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