Versions Compared

Old Version 19

changes.mady.by.user Unknown User (m.schadd)

Saved on

compared with

New Version 20

changes.mady.by.user Unknown User (m.schadd)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. A WSDL file may only contain 1 service, 1 binding and 1 portType definition. If you need more of these elements, create a separate WSDL files and import them separately.

     

    UI Text Box
    typeinfo
    When sending a message to a deleted service/binding/portType, the behavior you see is that at runtime the message is not translated to data in your profile.
  2. The communication may only be done in document/literal style. Other styles are not supported.
  3. For the elements and data types used in the schema only the namespace http://www.w3.org/2001/XMLSchema is supported.
  4. WSDL:Fault messages are currently not supported, they are ignored.
  5. Chameleon Schemas not supported (http://www.xfront.com/ZeroOneOrManyNamespaces.html)
  6. For SimpleType Restrictions only the baseType is used. Restrictions on the domain are ignored (For example: <xs:maxInclusive value=“100”/> for a simpleType with base integer.)
  7. When you have multiple files, you have to zip them.
  8. No folders are allowed in ZIP files, they need to be 'flat'
  9. 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.
  10. When using BAAS, the WSDL should be WSI BP 1.2 compliant (http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html).
  11. Only XML and JSON communication is supported with REST services.
  12. Empty fields in a message (example: <Number></Number>) are parsed as unknown. The exception are string fields. Those are parsed as empty string (””).
  13. Substitution Groups are not supported.
  14. WS-Addressing is ignored out-of-the-box (http://www.w3.org/Submission/ws-addressing/), but you can use the ISoapMessageHandler interface to use this protocol (see How to modify a SOAP request before being sent)..
  15. WS-Security is ignored out-of-the-box (https://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf), but you can use the ISoapMessageHandler interface to use this protocol (see How to modify a SOAP request before being sent).
  16. WS-SecurityPolicy is ignored (http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/)
  17. WS-Trust is ignored (http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/ws-trust.html)
  18. WS-Secureconversation is ignored (http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/ws-secureconversation.html)
  19. WS-ReliableMessaging is ignored (http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.2-spec-os.html)

...