Endevor SOAP API Compatibility with Endevor V19

[Vaughn Marshall]

Hi all,

Please be advised that as of V19, we will be introducing some changes to our SOAP API to ensure the API adheres to Broadcom security standards.  These changes may result in some incompatibilities in any consumer applications that use this API.  In particular:

• If you are using Endevor WS SOAP v1.1, you will need to change the endpoint name to EndevorServiceHttpSoap12Endpoint
• The current Endevor Web Services version contains specific namespace prefixes in every response due to the manual assignment of namespaces to every element. With the new version of Endevor Web Services, namespaces will be assigned automatically, which means that the location of namespace definitions and namespace prefixes will be different from the current version of Endevor Web Services. This change should not affect the regular SOAP client, but if you have some utility which parses a SOAP response according to specific namespace prefixes or their location, please be ready to update its code.
• There will be a change in .wsdl file location - it will migrate from EndevorService?wsdl to EndevorService.EndevorServiceHttpSoap12Endpoint?wsdl .  Note - this will only be an issue if you need to regenerate client stubs from this wsdl.
• Response format update. Due to the implementation of a different data-binding mechanism, some get* responses could differ from the old version of Web Services. However, work on this issue is currently ongoing and we will try to avoid such changes.
• NOTE: there will be no impact on the REST API

If there are any questions or concerns, please reach out to me at [e-mail] and we will be happy to assist you.

Vaughn Marshall & the Endevor Team

[Vaughn Marshall]

Hi all, I'm pleased to announce that the Endevor Web Services SOAP framework has been upgraded and published as LU09867 for Endevor V19 with some additional changes.  Here are some updates from the development team:

1.  No need to migrate from SOAP 1.1 to 1.2 endpoint – both versions supported simultaneously as a separate services.

2.  The new SOAP framework doesn't support a single endpoint with several SOAP versions. In the new version of Web Services, each SOAP version published separately under its own endpoint:

- SOAP 1.1 service location: 
/EndevorService/services/EndevorService.EndevorServiceHttpSoap11Endpoint
- SOAP 1.2 service
location:  /EndevorService/services/EndevorService.EndevorServiceHttpSoap12Endpoint
- HTTP service
location:  /EndevorService/services/EndevorService.EndevorServiceHttpEndpointpoint

3.  Each service has its own WSDL file, which can be accessed with the addition of ?wsdl to the service URL.