How to pack attribute values in a soap request?

Question

Hello,
We are trying to make an external webservice call through GWWS.
The (soap) request contains an element which looks like:
+<Request Version="1.0" RequestID="11111111" TypeOfRequest="type1" Echo="false">+
+<Info>+
+<Account xmlns="http://something.com/Domain1/">ABCD1234</Account>+
+</Info>+
+</Request>+
We had created this soap request based on the WSDL provided to us by the webservice host.
We used a tool (like soapui) to generate the the above request.
To be able to make a service call to this webserive, we used the wsdlcvt to generate the fml32 field headers as:
wsdlcvt -i <provided wsdl> -o <baseoutput name>
However we could not find a way to pack in the the information related to the attributes.
In vain, we tried to use the option [-m] with wsdlcvt.
Since there are no field headers generated by the wsdlcvt for the attributes, we do not know how do we put values of "Version", "RequestID", "TypeofRequest", "Echo" attributes of the "Request" element in the webservice request.
Are we missing something here?
How can we populate/put information in the attributes of an element in a request?
Thank you.
Sincere Regards,
Mrugendra

Answer 1

Hello Xu,
We have a simple test wsdl as follows
+<?xml version="1.0" encoding="UTF-8"?>+
+<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://new.webservice.namespace" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://new.webservice.namespace">+
+<wsdl:types>+
+<xsd:schema targetNamespace="http://new.webservice.namespace" xmlns="http://new.webservice.namespace" elementFormDefault="unqualified" attributeFormDefault="unqualified">+
+<xsd:complexType name="Service_Type">+
+<xsd:sequence>+
+<xsd:element name="DateTime" type="xs:dateTime" nillable="true">+
+</xsd:element>+
+<xsd:element name="UUID" type="xs:string" nillable="true">+
+</xsd:element>+
+<xsd:element name="Status" nillable="true" minOccurs="0" maxOccurs="unbounded">+
+<xsd:complexType>+
+<xs:sequence>+
+<xs:element name="StatusDesc" type="xs:string">+
+</xs:element>+
+</xs:sequence>+
+<xsd:attribute name="StatusTyp" type="xs:string" use="required">+
+</xsd:attribute>+
+</xsd:complexType>+
+</xsd:element>+
+</xsd:sequence>+
+<xsd:attribute name="Version" type="xs:string" use="required">+
+</xsd:attribute>+
+<xsd:attribute name="Name" type="xs:string" use="required">+
+</xsd:attribute>+
+</xsd:complexType>+
+</xsd:schema>+
+</wsdl:types>+
+<wsdl:message name="GetServiceReq">+
+<wsdl:part name="ServiceReq" type="tns:Service_Type"/>+
+</wsdl:message>+
+<wsdl:message name="GetServiceRes">+
+<wsdl:part name="ServiceRes" type="tns:Service_Type"/>+
+</wsdl:message>+
+<wsdl:portType name="ServicePortType">+
+<wsdl:operation name="getService">+
+<wsdl:input message="tns:GetServiceReq"/>+
+<wsdl:output message="tns:GetServiceRes"/>+
+</wsdl:operation>+
+</wsdl:portType>+
+<wsdl:binding name="ServiceBinding" type="tns:ServicePortType">+
+<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>+
+<wsdl:operation name="getService">+
+<soap:operation soapAction="getService"/>+
+<wsdl:input>+
+<soap:body use="literal"/>+
+</wsdl:input>+
+<wsdl:output>+
+<soap:body use="literal"/>+
+</wsdl:output>+
+</wsdl:operation>+
+</wsdl:binding>+
+<wsdl:service name="Service">+
+<wsdl:port name="getService" binding="tns:ServiceBinding">+
+<soap:address location="No Target Adress"/>+
+</wsdl:port>+
+</wsdl:service>+
+</wsdl:definitions>+
When we create a soap request (Using soapiu) from the above wsdl we get:
+<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">+
+<soapenv:Header/>+
+<soapenv:Body>+
+<ServiceReq Version="?" Name="?">+
+<DateTime>?</DateTime>+
+<UUID>?</UUID>+
+<!--Zero or more repetitions:-->+
+<Status StatusTyp="?">+
+<StatusDesc>?</StatusDesc>+
+</Status>+
+</ServiceReq>+
+</soapenv:Body>+
+</soapenv:Envelope>+
As you can see that ServiceReq has attributes Version and Name
However, wsdlcvt (with -m) creates the following fml32 headers
DateTime        1       string  -       fullname=DateTime, schema=xs:dateTime
ServiceReq      2       fml32   -       fullname=ServiceReq, schema=tns:Service_Type
ServiceRes      3       fml32   -       fullname=ServiceRes, schema=tns:Service_Type
Status  4       fml32   -       fullname=Status, schema=tns:Status
StatusDesc      5       mbstring        -       fullname=StatusDesc, schema=xs:string
UUID    6       mbstring        -       fullname=UUID, schema=xs:string
The points that we did not understand:
1. You mentioned: "SALT will map the *whole* request to FLD_MBSTRING
It is not so in this case.
Did we miss something?
2. Going by your suggestion in your last reply how do we create the FML32 buffer (specifically for the "ServiceReq" element, with attributes) for the sample we have?
Thank you.
Sincere Regards,
Mrugendra