Any possibility to understand Delphi?

[superomega]

Hallo,

with gSoap I don't have problems to talk at the moment.
But with Delphi 6 of course:

When I speak with a JavaClient to my WebService the message looks like this -->

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
 <S:Body>
 <ns2:echo xmlns:ns2="http://ws.wh.org/">
 <hallo>Stefan</hallo>
 </ns2:echo>
 </S:Body>
</S:Envelope>

Delphi is writing this message:

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <SOAP-ENV:Body>
 <echo xmlns="http://ws.wh.org/">
 <hallo>juhu</hallo>
 </echo>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Is there any possibility to understand the delphi message?

When I write a simple response back to delphi (for example a String) Delphi understands the response. But when I want to write back a array the understand is failing.
It seems that for some clients I have to know more about the content of the envelope. And sometimes to change the content. Is this the correct way?

Do anybody have some tips for this problem?
I think webservices are a nice technology but anything else than easy to handle.

Thank you very much,
Werner

[heiko.braun]

When I speak with a JavaClient to my WebService the message looks like this

What exactly do you mean with JavaClient? JBossWS? What version?

[superomega]

I use JBossWS 1.2.0 the actual version from last week.
The JavaClient runns with JDK 1.5.07 and is a stand alone Application.
The SOAP Libs that are used from the JClient are from JAX-WS 2.1

Java is making no problems.

But because of the kind of use of the namespaces in Delphi seems that the JBossWS Server is not understanding the message from the Delphi(6)-Client.

Greets,
Werner

[pliniker]

I thought I'd post my solution to this here as I've spent a day looking for a solution to the same problem, and only finding posts such as this without answers.


I have a JBossWS service that I am connecting a legacy Borland C++ app to, and ran into this same problem: the missing namespace.


In the WSDL Importer generated code, change the line with RegisterInvokeOptions to:

InvRegistry()->RegisterInvokeOptions(__interfaceTypeinfo(MyWebService), (ioDocument, ioLiteral, ioHasNamespace));

I can't see how to get WSDL Importer to generate this though.