problem accessing webservice

I am using a Delphi2007 webservice client to access a nonDelphi webservice.

The SOAP Request is being sent with no values.

The WSDL has a complex type
<xsd:complexType name="statusChange"><xsd:sequence>
<xsd:element name="candidateid" type="xsd:string" />
<xsd:element name="jobid" type="xsd:string" />
</xsd:sequence></xsd:complexType>
I am using a procedure that uses the complextype:
function  in_progress(const Value: statusChange): WideString; stdcall;

When I call the in_progress procedure, the XML request chops out all the 
values of the complextype

Here is what the request looks like:

<SOAP-ENV:Body 
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:NS2="urn:test_check">
<NS1:in_progress xmlns:NS1="JobSeeker"><Value
href="#1"/></NS1:in_progress>
<NS2:statusChange id="1"
xsi:type="NS2:statusChange"/>
</SOAP-ENV:Body></SOAP-ENV:Envelope>

This is what the request should look like:

The request should look like this
<SOAP-ENV:Body 
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:NS2="urn:test_check">
<NS1:background_check_in_progress
xmlns:NS1="JobSeeker"><Value 
ref="#1"/></NS1:in_progress>
<NS2:statusChange id="1" xsi:type="NS2:statusChange">
<candidateid xsi:type="xsd:string">332</candidateid>
<jobid xsi:type="xsd:string">22</jobid>'
</NS2:statusChange>
</SOAP-ENV:Body></SOAP-ENV:Envelope>

Any suggestions appreciated

Gerald 

I resolved the problem.
The WSDL importer does not correctly import complextypes. I created these 
manually and had ommitted registering them.
Once I registered them and declared them correctly all worked fine.
G

"Gerald" <gm@dataforcesoftware.com> wrote in message 
news:47b38914@newsgroups.borland.com...
>I am using a Delphi2007 webservice client to access a nonDelphi webservice.
>
> The SOAP Request is being sent with no values.
>
> The WSDL has a complex type
> <xsd:complexType name="statusChange"><xsd:sequence>
> <xsd:element name="candidateid" type="xsd:string"
/>
> <xsd:element name="jobid" type="xsd:string" />
> </xsd:sequence></xsd:complexType>
> I am using a procedure that uses the complextype:
> function  in_progress(const Value: statusChange): WideString; stdcall;
>
> When I call the in_progress procedure, the XML request chops out all the 
> values of the complextype
>
> Here is what the request looks like:
>
> <SOAP-ENV:Body 
>
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:NS2="urn:test_check">
> <NS1:in_progress xmlns:NS1="JobSeeker"><Value 
> href="#1"/></NS1:in_progress>
> <NS2:statusChange id="1"
xsi:type="NS2:statusChange"/>
> </SOAP-ENV:Body></SOAP-ENV:Envelope>
>
> This is what the request should look like:
>
> The request should look like this
> <SOAP-ENV:Body 
>
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:NS2="urn:test_check">
> <NS1:background_check_in_progress
xmlns:NS1="JobSeeker"><Value 
> ref="#1"/></NS1:in_progress>
> <NS2:statusChange id="1"
xsi:type="NS2:statusChange">
> <candidateid xsi:type="xsd:string">332</candidateid>
> <jobid xsi:type="xsd:string">22</jobid>'
> </NS2:statusChange>
> </SOAP-ENV:Body></SOAP-ENV:Envelope>
>
> Any suggestions appreciated
>
> Gerald
> 

Hello Gerald,

Thanks for the follow up post. This complex type looks pretty simple. If
time allows can you email me the schema/wsdl as I'm curious why the importer
failed to import such a simple declaration. I am aware of issues involving
nested compositor nodes, specially with cardinality specified on the
compositor nodes but your case is a simple sequence with plain strings....
something we should handle properly. Thank you.

Cheers,

Bruneau.

I have emailed the WSDL to you

G


"Jean-Marie Babet" <bbabet@borland.com> wrote in message 
news:47b47c2e$1@newsgroups.borland.com...
> Hello Gerald,
>
> Thanks for the follow up post. This complex type looks pretty simple. If
> time allows can you email me the schema/wsdl as I'm curious why the 
> importer
> failed to import such a simple declaration. I am aware of issues involving
> nested compositor nodes, specially with cardinality specified on the
> compositor nodes but your case is a simple sequence with plain strings....
> something we should handle properly. Thank you.
>
> Cheers,
>
> Bruneau.
>
>