The XML Schema WSDL data type in the WSDL Types column is based on "XML Schema: DataTypes" (XSD), which is now recommended by W3C. This document has three versions (1999, 2000/10, 2001), so which version must be indicated in the
XMLns: xsd = "http://www.w3.org/2001/xmlschema"
In this article, I will only consider the 2001 version. The recommender of the WSDL standard strongly recommends using the 2001 version.
In this column and in the future, you need to use the following short reduction or prefix
Namespace prefix stands for description Soapenchttp: //schemas.xmlsoap.org/soap/encodingSOAP 1.1 encodingWsdlhttp: //schemas.xmlsoap.org/wsdl/soapWSDL 1.1Xsdhttp: //www.w3.org/2001/XMLSchemaXML Schema
XSD base type
The following table is taken directly from the MSTK2 document, which lists all XSD base types supported by MSTK2. It also tells how the WSDL reader in the client or server is mapped to the Type of the XSD type to the corresponding type in VB, C , and IDL.
XSD (Soap) type variable type VBC IDLCommentsanyURIVT_BSTRStringBSTRBSTR base64BinaryVT_ARRAY | VT_UI1Byte () when SAFEARRAYSAFEARRAY (unsigned char) BooleanVT_BOOLBooleanVARIANT_BOOLVARIANT_BOOL ByteVT_I2Integershortshort range conversion verify the validity DateVT_DATEDateDATEDATE time is set oo: oo: ooDateTimeVT_DATEDateDATEDATE DoubleVT_R8Doubledoubledouble DurationVT_BSTRStringBSTRBSTR not take effect ENTITIESVT_BSTRStringBSTRBSTR conversion and does not convert and become effective ENTITYVT_BSTRStringBSTRBSTR when not convert and become effective FloatVT_R4Singlefloatfloat GDayVT_BSTRStringBSTRBSTR not convert and become effective GMonthVT_BSTRStringBSTRBSTR not convert and become effective GMonthDayVT_BSTRStringBSTRBSTR not convert and become effective GYearVT_BSTRStringBSTRBSTR not convert and become effective GYearMonthVT_BSTRStringBSTRBSTR not convert and become effective IDVT_BSTRStringBSTRBSTR not convert and become effective IDREFVT_BSTRStringBSTRBSTR not convert and become effective IDREFSVT_BSTRStringBSTRBSTR not convert and become effective IntVT_I4Longlonglong IntegerVT_DECIMALVariantDECIMALDECIMAL conversion range range effective upon the entry into force LanguageVT_BSTRStringBSTRBSTR not take effect LongVT_DECIMALVariantDECIMALDECIMAL conversion and conversion and conversion NameVT_BSTRStringBSTRBSTR not take effect NCNameVT_BSTRStringBSTRBSTR not convert and become effective range negativeIntegerVT_DECIMALVariantDECIMALDECIMAL conversion and conversion into effect NMTOKENVT_BSTRStringBSTRBSTR not take effect NMTOKENS VT_BSTRStringBSTRBSTR not converted into force and become effective range range nonPositiveIntegerVT_DECIMALVariantDECIMADECIMAL it effective normalizedStringVT_BSTRStringBSTRBSTR NOTATIONVT_BSTRStringBSTRBSTR when nonNegativeIntegeVT_DECIMALVariantDECIMALDECIMAL conversion does not convert and become effective range QnameVT_BSTRStringBSTRBSTR take effect when NumberVT_DECIMALVariantDECIMALDECIMAL positiveIntegerVT_DECIMALVariantDECIMALDECIMAL conversion does not convert and become effective ShortVT_I2Integershortshort StringVT_BSTRStringBSTRBSTR TimeVT_DATEDateDATEDATE date to December 30, 1899 and does not convert into effect unsignedByteVT_UI1Byteunsigned TokenVT_BSTRStringBSTRBSTR range commencement XSD defines two built-in data type conversion range commencement unsignedShortVT_UI4LongLongLong range commencement unsignedLongVT_DECIMALVariantDECIMALDECIMAL conversion charunsigned char UnsignedIntVT_DECIMALVariantDECIMALDECIMAL conversion: original and derived. It is very beneficial to review the level of the internal data type below:
