LDBWS wsdl doesn't play nice with autodiscovery

[Matt Harker]

I've been trying to access the LDBWS interface via a node.js library, node-soap (https://github.com/vpulim/node-soap), which simplifies the procedure of sending SOAP requests by parsing the WSDL, creating methods for each of the operations available, and also ensuring that the right namespaces are included in any requests.

However, it seems like the LDBWS wsdl is actually incomplete as far as namespaces goes, as it doesn't include any namespace which actually includes the AccessToken element required for authentication. While I appreciate that that namespace isn't actually required for the actual definition of the wsdl, the fact that it's not included and not referenced at all makes the autodiscovery used by node-soap (And probably other libraries) completely non-functional.

To get around this i've had to download the wsdl to a local directory and augment the definition to include a reference to the namespace defined by http://thalesgroup.com/RTTI/2010-11-01/ldb/commontypes,  which then makes the autodiscovery work.

Is it possible to update the actual wsdl hosted to include this reference?

[Derek Goodwin]

The LDBWS wsdl does include a reference, it's right at the top

<wsdl:import namespace="http://thalesgroup.com/RTTI/2013-11-28/Token/types" location="darwin_token_types_2013-11-28.wsdl"/>

[ja...@famnoon.com]

Have you had any luck with this? I'm migrating from PHP to node and its proving a nightmare!

[Tom Lane]

Vaguely related note: This works fine with the Visual Studio .net wsdl parsing/generation.