Not sure why the generated WSDL is inconsistant but as a workaround you can
add a "" tag to the WSDD and point to your WSDL. I usually do that to
let my clients see the WSDL I coded, instead of an Axis generated one.
TMG <[EMAIL PROTECTED]> wrote:
I would like to add a header to several of my servi
response element that you get back from the service (RequestDataResponse) doesn't match the WSDL (ResponseData). Is the Web
service doing its own thing? What exactly is the error that you get from the Systinet client?Tony "Sathya Sankar" <[EMAIL PROTECTED]> wrote on 09/12/2004 20
I'm trying to understand how the response messages are formatted for a Document Literal service. I have attached the WSDL I'm working with.
The request that gets sent (using the Axis test client) looks good to me. The "Data" gets wrapped into "RequestData" and goes out.
http://schemas.xmlsoap
I've been using Axis 1.1 for a while and recently needed to work with attachments. I thought of moving to the 1.2 version since it has better support for those.
Here is my scenario... I'm using Axis (generated classes & its libraries) to talk to another server using Wrapped/Literal. The WSDL tha
