parameter not being passed correctly in wsdl (delphi)

did you mean "wslimporter" instead of "wdlimporter"?

What version of Delphi are you using?

Is it possible that any of the parameter names have changed case?

Sorry for the delay been on holiday just got back.

I am on delphi 2007, the wsdl file is new and we are testing it out.
I used the wsdl importer off the webservices (new item) to generate the unit.

I have re-downloaded the wsdl from the url given, and it generates the same unit.

I can sent the wsld but it is IP restricted for testing

Is it possible that the WSDL file is incorrect?

how would I know if it wasn't. ?  I am a novice on webservices.
The wdsl file is generated by a multi national company so I assume it is correct.
But maybe it isnt for (I shouldnt make assumptions).

I tried it using SoapUI, and it worked, but had to 'bind' the endpoints before it would work.
but cant see a similar thing in the delphi help file

What sort of thing should I be looking for ?

Shattered from coming back from holiday, will pick up any reply in the morning (UK time)

In the wdsl generated unit I have calls like

    function  getpropertybyuprn(const uprn: Int64): WideString; stdcall;
     function  getpostcode(const postcode: WideString): WideString; stdcall;
end;

function Getnlpgweb(UseWSDL: Boolean=System.False; Addr: string=''; HTTPRIO: THTTPRIO = nil): nlpgweb;


I then call the code

str := getnlpg(false, '').getpropertyuprn(123456);

or

str := getnlpg(false, '').getpostcode('AB1 1TJ');

passing across a number give the impression of zero being passed. Passing the string gives
a java null string error.
----------------------------------------------------------------------

I will check on my version of delphi 2007 and patches and get back to you.

I think you have to cast the string as a wide string and number as int64.

I tried that in the sense, I declared 2 varaibles

uprn : int64;
postcode  : widestring;

as this is how I started.

I have gone back to trying the wdslimp from the codegear bin directory.

If I I call it

wsdlimp -0l+ -P test.wsdl

when the test.wsdl has my wsld file in, then in the command line I get
Reading: test.wsdl
Import: test.wsdl:0
*Error*:  followed by the schema location on the 3rd parties servers

If I look at the generated test.pas file I find comments like

// The following types, referred to in the WSDL document are not being represented
// in this file. They are either alaises [@} of other types represented or were referred
// to but never[!] declared in the document. The types from the latter. The types from the latter
// category typically map to the predefined/known xml or Borland types; however; they also could
//indicate incorrect wsdl documents that failed to declare or imoprt a schema type

Does this mean that the wsdl or the xml generated from the 3rd party company is erroreous

did you do something like this?

uprn : int64;
postcode  : widestring;
 
uprn := 123456;
str := getnlpg(false, '').getpropertyuprn(uprn);
 
postcode :=  'AB1 1TJ';
str := getnlpg(false, '').getpostcode(postcode);

                                              

1:
2:
3:
4:
5:
6:
7:
8:

yes

are you sure it is -f

if I try

wsdlimp -f -P test.wsdl

it says invalid option, similarly

wsdlimp -Of- -P test.wsdl

gives an invalid optionn

oops.  Ignore the -f comment.  That pertains to a different WSDL importer.