Per today's (7/31/18) DESDL project call, this item was deemed High priority and needs to be included in the HPCC 7.0.0 release.

Here is the design (agreed by Tony):

- Add an option in the esp service binding to specify namespace template

• The template is an XPATH, with possible variables and functions

• The following variables are predefined:

  • version

  • service: the mixed case service name (as defined in ecm file)

  • method: the mixed case method name

So for WsAccurint namespace, the namespace template is:

http://webservices.seisint.com/$service

For WsHealthcare (using esdl_svc_engine), the namespace template is:  

concat(‘rn:lnrisk:ws:’,lower-case($service),’:@ver=’,$version)

Note that the following does not work (due the special character @ in it: @ver will be treated as attribute ver):

rn:lnrisk:ws:lower-case($service):@ver=$version

From: Pastrana, Rodrigo (RIS-BCT)
Sent: Tuesday, May 08, 2018 12:47 PM
To: Gao, Jiafu (RIS-BCT) <Jiafu.Gao@lexisnexisrisk.com>; Ma, Yanrui (RIS-BCT) <Yanrui.Ma@lexisnexisrisk.com>
Cc: Fishbeck, Anthony (RIS-BCT) <Anthony.Fishbeck@lexisnexisrisk.com>; Klemm, Tim (RIS-BCT) <Tim.Klemm@lexisnexisrisk.com>
Subject: RE: Dev server for Dynamic ESDL testing

We found a few discrepancies between the oss and scapps WSDLs and will put them here for discussion:

1 – OSS targetnamespace reports methodname if available

2 – OSS targetnamespace reports esdl optionals encapsulated in params immediately following service/methodname

3 - OSS targetnamespace reports version delineated by @

4 – OSS wsdl:service/wsdl:port/soap:address/@location reports address:port (no service/method URI, nor url params)

• Scapps provides address:port/service?urlparams

5 -   OSS binding/soap:binding /operation/soap:operation/@soapAction seems to always prefix the literal “custom” followed by methodname ?ver_=X.Y

• Scapps Servicename/methodname?URLparmas including optionals &ver_=x.y

@Rodrigo Pastrana can you enumerate what the WSDL issues were?

I think 1 was a bug in the way the SOAP ACTION was formed.

Yes, for the namespace I think we need a way of configuring the exact literal value,..

but things like client version still need to be added at runtime, so perhaps a configured value that can include a few variables.

For example, you could configure:

<namespace>http://x/y/z?ver_=\{clientVersion}</namespace>

Just a suggestion, we can work out the details.