1999 soap schema versus 2001

Question

I'm having 3rd party integrating with our product.
They had some problems with the client.
It appears that 2 identical SOAP messages aside from some attributes in <SOAP-ENV:Envelope> have different results. One works and the other doesn't:
Working
=======
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
                    xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
                    xmlns:xsd="http://www.w3.org/1999/XMLSchema">
Not working
===========
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
                    SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
                    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
The one which doesn't work send back a respose saying it there has been a deserialization error due to error in type mapping. And it leasts all the entries. I included some as an example
xsd_type: ['java:com.symantec.eb.renewal.ws']:p36:ArrayOfEbRenewProducts
ser: com.symantec.eb.renewal.ws.ArrayOfEbRenewProductsCodec@1acb490
deser: com.symantec.eb.renewal.ws.ArrayOfEbRenewProductsCodec@1826d42
(see Fault Detail for stacktrace)</faultstring><detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">weblogic.xml.schema.binding.DeserializationException: type mapping lookup failure on type=java:com.symantec.eb.renewal.ws:EbGetCouponRequest TypeMapping=TYPEMAPPING SIZE=36
ENTRY 1:
class: com.symantec.eb.renewal.ws.EbUpdateSessionStateResponse
xsd_type: ['java:com.symantec.eb.renewal.ws']:p20:EbUpdateSessionStateResponse
ser: [email protected]f8
deser: [email protected]526
ENTRY 2:
class: com.symantec.eb.renewal.ws.EbRedeemCouponResponse
xsd_type: ['java:com.symantec.eb.renewal.ws']:p9:EbRedeemCouponResponse
ser: com.symantec.eb.renewal.ws.EbRedeemCouponResponseCodec@cbeeda
deser: com.symantec.eb.renewal.ws.EbRedeemCouponResponseCodec@ae630a
ENTRY 3:
class: com.symantec.eb.renewal.ws.EbRenewSubResponse
xsd_type: ['java:com.symantec.eb.renewal.ws']:p11:EbRenewSubResponse
ser: com.symantec.eb.renewal.ws.EbRenewSubResponseCodec@e82d0d
deser: com.symantec.eb.renewal.ws.EbRenewSubResponseCodec@e5df1b
I'm using Weblogic 8.1 SP3. Any ideas?

Answer 1

SOAP is a strange animal, there are many variances of it. AS SOAP falls in the thick of of.
To use AS SOAP, you must find a SOAP service that is compatible to AS. I recommend you to visit: http://www.xmethods.com/ve2/index.po
xmethod has a (very) full list of SOAP services, but you must look for RPC services other services won't seem to work.
Once you find the service of your need, you need to look at its RPC profile, I often use: http://www.cosme.nu/services/pop.php to check my POP3 incoming mails.
This is the service: http://www.cosme.nu/services/pop.php
Click on countmessages for the profile, the profile include all info to write AS SOAP handler.
This is my handler (part of a script):
on getPOPmessageCount(popserver, _popserverport, _login, _password)
tell application "http://www.cosme.nu/services/pop.php"
set POPmessageCount to (call soap ¬
{method name:"countmessages", method namespace uri:"http://www.cosme.nu/services/", parameters:¬
{popserver:_popserver, popserverport:_popserverport, login:_login, |password|:_password} ¬
, SOAPAction:"http://www.cosme.nu/services/pop.php"})
end tell
return POPmessageCount
end get_POPmessageCount