Page History
...
Blueriq supports the WSDL 1.1 standard. It consists of service, binding, portType, message and type definitions. There are additional restrictions on the WSDL files:
| What | Baas |
|---|
| SOAP | Baas |
|---|
| REST | Webservice Client |
|---|
| (SOAP) | Webservice Client |
|---|
| (REST) |
|---|
| SOAP Service Client | Notes | |||||
|---|---|---|---|---|---|---|
| Containment of a WSDL file | 1 service 1 binding 1 portType | 1 service 1 binding 1 portType | 1 service 1 binding 1 portType | 1 service 1 binding 1 portType | 1 service 1 binding 1 portType | If you need more of these elements, create a separate WSDL files and import them separately. |
| ||||||
| Communication style | Document/literal | Document/literal | Document/literal | Document/literal | Document/literal | |
|---|---|---|---|---|---|---|
| Elements and data types | Only the namespace XMLSchema is supported* | Only the namespace XMLSchema is supported* | Only the namespace XMLSchema is supported* | Only the namespace XMLSchema is supported* | Only the namespace XMLSchema is supported* | |
| WSDL:Fault messages | Not supported, they are ignored | Not supported, they are ignored | Not supported, they are ignored | Not supported, they are ignored | Supported, soap fault and message can be mapped to the profile | |
| Chameleon Schemas | Not supported (link) | Not supported | Not supported | Not supported | Not supported | |
| SimpleType Restrictions | Only the baseType is used | Only the baseType is used | Only the baseType is used | Only the baseType is used | Only the baseType is used | Restrictions on the domain are ignored (For example: <xs:maxInclusive value=“100”/> for a simpleType with base integer.) |
| Multiple files | you have to zip them | you have to zip them | you have to zip them | you have to zip them | you have to zip them | |
| Folders in zip files | No folders are allowed in ZIP files, they need to be 'flat' | No folders are allowed in ZIP files, they need to be 'flat' | No folders are allowed in ZIP files, they need to be 'flat' | No folders are allowed in ZIP files, they need to be 'flat' | No folders are allowed in ZIP files, they need to be 'flat' | |
| Webservice location | The webservice has to be in the entry point module, or a mapping has to be made between the entrypoint module and the webservice module | The webservice has to be in the entry point module, or a mapping has to be made between the entrypoint module and the webservice module | ||||
| WSI BP 1.2 compliant | The WSDL should be WSI BP 1.2 compliant (Link) | The WSDL should be WSI BP 1.2 compliant | ||||
| Communication | XML and JSON communication is supported * | XML and JSON communication is supported * | ||||
| What | Baas |
| SOAP | Baas |
|---|
| REST | Webservice Client |
|---|
(SOAP) | Webservice Client |
|---|
(REST) |
|---|
| SOAP Service Client | Notes | |||||
|---|---|---|---|---|---|---|
| Empty fields in a message (example: <Number></Number>) | Are parsed as unknown when mapped to attributes. The exception are string fields. Those are parsed as empty string (””). Are parsed as instances when mapped to relations. | Are parsed as unknown when mapped to attributes. The exception are string fields. Those are parsed as empty string (””). Are parsed as instances when mapped to relations. | Are parsed as unknown when mapped to attributes. The exception are string fields. Those are parsed as empty string (””). Are parsed as instances when mapped to relations. | Are parsed as unknown when mapped to attributes. The exception are string fields. Those are parsed as empty string (””). Are parsed as instances when mapped to relations. | Are parsed as unknown when mapped to attributes. The exception are string fields. Those are parsed as empty string (””). Are parsed as instances when mapped to relations. | |
| Substitution Groups | Not supported | Not supported | Not supported | Not supported | Not supported | |
| WS-Addressing | Ignored out-of-the-box (Link) | Ignored out-of-the-box | Ignored out-of-the-box | Ignored out-of-the-box | Ignored out-of-the-box | You can use the ISoapMessageHandler interface to use this protocol (see How to modify a SOAP request before being sent) |
| WS-SecurityPolicy | Ignored (Link) | Ignored | Ignored | Ignored | WS-Security support by using | |
| WS-Trust | Ignored (Link) | Ignored | Ignored | Ignored | ||
| WS-Secureconversation | Ignored (Link) | Ignored | Ignored | Ignored | Ignored | |
| WS-ReliableMessaging | Ignored (Link) | Ignored | Ignored | Ignored | Ignored | |
| Document attachements | Not supported | Not supported | Not supported | Not supported | Document attachments can be send using MTOM |
* Blueriq supports XML version 1.0, not 1.1. As the versions are very similiar similar to each other, importing 1.1 should work as long you do not use the unique features of 1.1. Blueriq does however not support 1.1, and any issues have to be resolved by yourself.
...
- The message has to be contained in either curly braces ( { key : value } for standard JSON messages) or brackets ( [ value ] for messages that start with an unnamed array). Information on how to define REST message bodies through domain schemas can be found here: Domain schema editor
An array cannot contain mixed content
For example this response that mixes an attribute with an object is not supported:Code Block { [ 3, {} ] }
Overview
Content Tools