I have a server with a TROIpSupperHTTPServer and this has 2 messages: a TROBinMessage and a TROSOAPMessage.
When I call http://localhost:8100/soap I get a list of the services availble in the library. When I click on a service however it just return the same page and not the wsdl for that service. I have set the xsoSplitServiceWSDLs to true and SoapMode to sDocumentLiteral.
Exactly, that is a bug and don’t allow to import into delphi a soap rem objects service. That is an old problem, not resolved yet. Even if you invoke using the service url the result cannot be imported on delphi.
If that i solved, we can use easily remobjects servers with delphi mobile (yes, just in a less integrated way, but is a fact we can), so please resolve this problem ASAP.
As you won’t support Delphi mobile directly then PLEASE fix this. I am desperately looking for a method to use my RO servers with Delphi Mobile and do not want to have recode everything in Datasnap. RO might not like Delphi’s solution but some (possibly a lot) of your customers do want to use it and as seamlessly as possible. Please let us know that you will fix this issue. Thanks
@slavad do you mean the incompatible and non standard WSDL generation is related to a channel???
I use synapse htttp server, so this channel will not have the problem resolved? I don’t get at all. Please clarify this point.
So does this mean that the fix will enable the message to return the wsdl - but this won’t be a standard definition so will not be importable into Delphi?
@russellweetch just add a indy http server and get from then the definition, will work on delphi. Then you can safely remove it and continue using synapse channels.