On Mon, Sep 26, 2011 at 8:01 PM, Paul Boniol <[email protected]> wrote:

> On Fri, Sep 23, 2011 at 8:45 PM, Paul Boniol <[email protected]>wrote:
>
>> I had some even higher priority things come up, but I'm back to SOAP
>> now...  I'm seriously considering chucking SOAP::Lite as recommended, but I
>> also feel what the code I have is very close to working.
>>
>> From what I can tell, the server doesn't know what to do with the
>> "xsi:type" attributes that SOAP::Lite puts in automatically, and so it
>> fails.  I can't seem to find a way to tell SOAP::Lite not to put these in...
>>
>>
>> The specific error is:
>> Castor unmarshalling exception: The namespace associated with the prefix
>> 'xsi' could not be resolved.
>>
>> <snip>
>>
>

> Okay.. I overlooked the somewhat obvious.  To get rid of things like
> xsi:type="xsd:string", add
> ->type('')
> to any data that has a value.  It works now.
>
> Paul
>

Well, now that I found this, I found what it is called, autotype.  Once I
had a name it was easy to find additional ways to turn it off.

In addition to the method of

adding   ->type('')   to any data with values
or
$soap->autotype(0);     # this works
or
sub typelookup { return undef; }  # have not tried

Paul

-- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en

Reply via email to