Anne,
Answers to your questions - Why you selected message style? Message style is used by the architects considering interoperability issues in mind. They want to receive the XML and send back the XML and do not want to deal with the SOAP engine serialization. It provide the web service more freedom and we do not jump into the issues of mapping the complex types across platforms - Does the message have a defined message structure, or was your goal to enable the exchange of any content? It is pure message based and we are not passing any content (attachments) in the web service. We have defined unqualified schemas for request and response and negotiate on those schemas while sending the request and response. - Did you write a WSDL with a defined schema for the message structure? I generated the WSDL from the Apache Axis by appending ?WSDL to the web service URL. I have attached the WSDL with this email. Unfortunately .Net client cannot understand this WSDL and they want to change the WSDL manually and include the schema definition in it. - What are the challenges that .NET clients are facing? .Net Client chaged the WSDL file “whatever.wsdl” and after that they are able to invoke the web service. I turned on the Tcp trace and can see a valid request and response getting exchanged. The problem is that when ever .Net gets back a response it is not able to return the object back to the .Net program. I am confused and thinking it might be a problem with the namespaces or structure of the XML document which is getting passed in the response of the web service. My understanding is that .Net is trying to de-serialize the response by matching the response XML with the schema in WSDL but not able to do so. Do you see any problem in the WSDL? How is it normally done when we use message style web services and have .Net Client. Appreciate your response. _____ From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 30, 2007 11:58 AM To: Gurpreet Singh Dhanoa, HCL-Industry Solutions Subject: Re: Help with Message Style Web services Please ask your questions on the Axis forum. Please include answers to the following questions: - Why you selected message style? - Does the message have a defined message structure, or was your goal to enable the exchange of any content? - Did you write a WSDL with a defined schema for the message structure? - What are the challenges that .NET clients are facing? Anne On 1/30/07, Gurpreet Singh Dhanoa, HCL-Industry Solutions <HYPERLINK "mailto:[EMAIL PROTECTED]"[EMAIL PROTECTED]> wrote: Hi Anne, I got your email id from the Axis forum. I have published some web services on message style basis for our customer. I have got a .net client which is facing problems while de-serializing the response back. Do you know of any way or know any reference where this Axis message style web services are in use? I will appreciate your response! Regards -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.8/649 - Release Date: 1/23/2007 8:40 PM DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.8/649 - Release Date: 1/23/2007 8:40 PM -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.17/661 - Release Date: 1/30/2007 11:30 PM
ECMGetDocument.wsdl
Description: ECMGetDocument.wsdl
whatever.wsdl
Description: whatever.wsdl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
