Service Studio provides extensive support for providing and consuming SOAP Web Services. However, due to the OutSystems Platform language expressiveness, there are scenarios that are only supported through extensions, using Integration Studio.
Integration Studio allows you not only to import Web Services from a .Net Assembly, but also implement custom logic to provide and consume Web Services in both .Net and Java.
In the following scenarios you need to implement custom extensions:
Types created via "restriction" over another type are normally the same as the latter type. Only the "maxLength" and "fractionDigits" restrictions are considered when creating the appropriate data types, but these restrictions are not enforced at runtime;
Types of "element" type with sub-type of "schema" type (i.e. dynamic schemas) are interpreted as a simple Text item;
Types of "simpleType" and sub-type that is not "restriction" (such as "list", a space-separated sequence of text atoms) are interpreted as a simple Text item;
Types of "complexType" and sub-type that is not "sequence", "all" or "complexContent" are interpreted as a simple Text item;
Sub-types of "complexContent" and sub-sub-type that is not "restriction" or "extension" are interpreted as a simple Text item;
When trying to consume a SOAP Web Service in Service Studio, if one of the scenarios described above is detected, Service Studio displays an Unsupported Consumed Web Service Error.
XML Data Types to eSpace Data Types