I'm trying to create a web service that uses soap for connections.
I can create it fine if I'm not specific about the names on request/response etc.
My problem is I need to be specific. I've watched the WSDL tutorials, XML, XSD, SOAP etc and every time I start my project I end up stuck.
For example, if I create a service called OTA_Ping the soap created by the .NET framework calls the request OTA_Ping and the Response OTA_PingResponse. I want it to be OTA_PingRS so I tried to name the method OTA_PingRQ. This works for the request but then names the response OTA_PingRQResponse. DOH! I've fooled around with WSDL's and XSD's as well to try and manipulate things but then read that the WSDL is simply there for the consumer, not to define the service. ARG.
Is there a tutorial out there that tells how to customise the entire SOAP in SOAP out?
I'd also like to include attributes in the OTA_PingRQ element. But have no idea how.
Should I return strings in my mehtods or xml text or xmlElements or xmlDocuments? I've read so many tutorials and simply can't put it all together.
Any direction will be much appreciated.
View Complete Post