[vwnc] Web Services and abstract wsdl schema types ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] Web Services and abstract wsdl schema types ?

T. Edwin King
VW76NC
 
I've been trying to use the VW tools with the NetSuite Web Service api (https://webservices.netsuite.com/wsdl/v2009_1_0/netsuite.wsdl), and I've used the WSDL Wizard to create the WsdlClient and Xml to Object binding code (and server code for a web service mock/stub).  Most things I've tried have worked fine, with the exception of a service method that takes an abstract type, SearchRecord, as the aspect of the input object (SearchRequest>>searchRecord: ) .
 
The problem that occurs is that when I set the searchRecord to an instance of one of SearchRecord's subclasses (e.g., AccountSearch), the SOAP message body only includes an empty SearchRecord element.  Following is an Http request that is generated when an instance of AccountSearch is provided as the searchRecord: 
 
POST /services/NetSuitePort_2009_1 HTTP/1.1
Host: webservices.sandbox.netsuite.com
SOAPAction: "search"
Content-type: text/xml;charset=utf-8
 
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="urn:messages_2009_1.platform.webservices.netsuite.com">
<SOAP-ENV:Body>
    <ns:search>
        <ns:searchRecord/>
    </ns:search>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
 
What happens, of course, is that on the service side the searchRecord can't be serialized into anything useful, since it is abstract.
 
So my question is: is this a known issue with the Wsdl binding tools?  Or is there some customizations that I need to make so that the SearchRecord subclasses are marshaled properly into the request?  ... or both?
 
Regards,
Todd E. King

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc