WSDL import does create invalid RODL

Remoting SDK
1

Hi

I try to import a WSDL into the newest V9 Service Builder. But the result shows an invalid parameter value

a) Import WSDL from the attached file Enterprise_V36_org.zip (55.4 KB)
b) Escape reserve words
c) Check Library
-> shows problems with an unknown type …
c1) if I use checked the import option “create wrapper” for nillable types -> NewLibary.value = unknown
c2) if I use unchecked the import option “create wrapper” for nillable types -> recordTypeInfos = unknown

very strange

2

Just tested the attached WSDL with SoapUI and it works fine. Any hint why the Service Builder fails to import the Service would be great.

3

We’re currently working on this. I’ll post an update here once we get a fix.

4

Hello

We’ve updated the SOAP importer module. Here is the imported RODL: Enterprise_V36_org.rodl (449.4 KB)

Regards

5

Looks better:). Could I kindly ask you to produce the RODL as well for the WSDL Enterprise_V36.zip (48.6 KB).

Please import the WSDL using
Disable “wrappers for nillable types”
String type mapping: “WideString”

This does allow me to integrate the resulting RODL & Interface to our test environment.
BTW: is there an easy way that a customer gets a fixed ServiceBuilder? (e.g. manually register the exchanged .NET assemblies somehow?).

6

Hello

Unfortunately registering an updated importer won’t be an easy task. As a workaround I’ve attached the imported RODL and the command-line version of the SOAP Importer tool. Start it w/o arguments to see the all possible options

F.e. for your settings (no wrapper structures and WideString as a string class) command line would look like

ROSoapImporter.exe -w:“Enterprise_V36.wsdl” --st=WideString

SoapImporter.zip (289.1 KB)
Enterprise_V36.rodl (95.1 KB)

Regards

7

thank you for the fast answer! I will test until the end of the week and will post the results.
best regards

8

The new SoapImporter works great and solves all the problems. Thank you.