Forum Discussion

lsushant's avatar
lsushant
New Contributor
17 years ago

Error message -Can't yet deserialize non-null Objects

Hi ,
How can i resolve the following error message .
Thu May 14 11:31:54 EDT 2009:DEBUG:<< "Can't yet deserialize non-null Objects[\n]"

3 Replies

  • Hi lsushant,


    This is most probably an error on the server side.
    I was not able to go deeper into the problem since you didn't attach MidasActionAPISoapHandler-binding.wsdl that is imported from the WSDL you've attached.

    If you still cannot figure out the problem, could you attach the imported WSDL as well?


    Cheers!
    /Nenad Nikolic a.k.a. Shonzilla
  • Hi Isushant,


    OK, so it's not the problem with the imported WSDL file.
    I'm falling back to my original suspicion - the fault is probably on the server side.

    It is the server reporting the fault I'm assuming something is wrong with how it processes the incoming SOAP request that was assembled by soapUI. You may want to start by checking how request arguments (apiNames, zone, xml, returnFormat) are handled by the server since these arguments can be anything (i.e. they're of xsd:anyType type)

    I hope you'll be able to find the root cause of this fault.


    Cheers!
    /Nenad Nikolic a.k.a. Shonzilla