Re: SOAP project

Thanks for the further followup Wessel,

As for those webservice which doesn't interop well between different
client/server, it is often caused by the message contract not well defined.
Generally, we are always recommended to define the message contract first
when buidling a certain XML WebService so as to increase the
interopability. This is often known as "Contract first" development, you
can also find may resources and articles discussing on this topic over the
net.

#Contract-First Service Development
http://msdn.microsoft.com/msdnmag/issues/05/05/ServiceStation/default.aspx

#Contract First Web Services Interoperability between Microsoft .NET and
IBM WebSphere
http://msdn.microsoft.com/vstudio/java/interop/websphereinterop/default.aspx

Hope also helps. Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)



--------------------
| Date: Fri, 22 Jul 2005 09:52:31 +0200
| Subject: Re: SOAP project
| References: <ePnGQWwiFHA.3012@xxxxxxxxxxxxxxxxxxxx>
<Ozet9dyiFHA.3608@xxxxxxxxxxxxxxxxxxxx>
<EpecOc0iFHA.3472@xxxxxxxxxxxxxxxxxxxxx>
<e06oIOVjFHA.576@xxxxxxxxxxxxxxxxxxxx>
<AW8358YjFHA.940@xxxxxxxxxxxxxxxxxxxxx> <op.st9aodk4f3yrl7@asbel>
<emDPa5ljFHA.944@xxxxxxxxxxxxxxxxxxxxx>
| From: "Wessel Troost" <nothing@xxxxxxxxxxxx>
| Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
| MIME-Version: 1.0
| Content-Transfer-Encoding: 8bit
| Message-ID: <op.sua1hto1f3yrl7@asbel>
| User-Agent: Opera M2/8.01 (Win32, build 7642)
| Newsgroups: microsoft.public.dotnet.languages.csharp
| NNTP-Posting-Host: beetslaan.demon.nl 83.160.164.142
| Lines: 1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.languages.csharp:111627
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| > message) is ok. BTW, how are you generating the SOAP message now ? Since
| > you've mentioend that you've got the XmlSchema of the classes and
message
| > format of the webservice, I think you can consider using the .NET
xsd.exe
| > tool to create the dot.net serializable classes which maps to the SOAP
| > messages. Thus, it'll much ease the message building work and make it
|
| When possible we use the web reference (wsdl.exe) which is the simple way.
|
| When there's no WSDL, we're generating the message by using a template
and
| filling in the variables. Thanks for the pointer to xsd.exe, I'll try
| that next time!
|
| There's even a web service written in Java that does publish WSDL, but
| does not interact nicely with .NET. One of the functions returns an
array
| that .NET cannot read. For that service we use the template-filling
| method too.
|
| Greetings,
| Wessel
|

.

Relevant Pages

  • Re: Converting an application to support Web Services ...
    ... I know what web services is ... want some details resources ... ... if u have Search function in some component and want extract it to the ... > WS the first step you need to undertake is to create contract. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • RE: Fighting WSDL.exe
    ... dealt with this in a while (totally jaded about web services, ... validation against the original WSDL file OR the original schema. ... creating code based on the contract since, as mentioned earlier, the contract ... If a document-literal binding in a DESCRIPTION does not specify the ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Fighting WSDL.exe
    ... The MS implementation of Web Services makes the assumption, at runtime, ... validation against the original WSDL file OR the original schema. ... wasting your time creating this contract first and then ... schema validation on input and on output, ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
Loading