SOAP project

M

MR

i need to develop a SOAP client, Since I have never personally done one I
would like to make sure that I am going about it correctly.
The client is a Windows (probably 2k3) application that communicates over
HTTPS SOAP. The remote server is Unix based and implements Axis, which I
know nothing about

What are the steps I need to create this client? I will be developing in C#
and I have the XML schema of the SOAP messages.
How do I get started?
thanks for your help
m
 
W

Wessel Troost

What are the steps I need to create this client? I will be developing in
C# and I have the XML schema of the SOAP messages.

Try to add a "web reference". If that works, the rest of the client is a
breeze.

Greetings,
Wessel
 
P

Peter Bromberg [C# MVP]

Find out if the Server produces an industry standard "WSDL" contract xml
document. If it does, your job is much easier - you can create a SOAP proxy
class from the WSDL directly. Otherwise,
you will need to create classes based on the SOAP Schema, and submit them to
the server as standard SOAP messages.
Peter
 
S

Steven Cheng[MSFT]

Thanks for Peter's informative suggestions.

Hi RM,

As Peter has mentioned, for consuming a certain XML WebServcice in our
clientside appolication, the most important is to get a copy of the
webservice's WSDL document since the WSDL is the contract of the webservice
which define the type system and message format and service specific infos.
I think the apache axis should has its own means to expose such
description. After you get it, we can use the WSDL.exe (or the
AddWebReference feature in VS.NET) to help generate the .net classes for
consuming the webservice. Anyway, I think we can start from this.

#Web Services Description Language Tool (Wsdl.exe)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/htm
l/cpgrfwebservicesdescriptionlanguagetoolwsdlexe.asp

Hope also helps.

Steven Cheng
Microsoft Online Support

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




--------------------
| From: "Peter Bromberg [C# MVP]" <[email protected]>
| References: <[email protected]>
| Subject: Re: SOAP project
| Date: Sun, 17 Jul 2005 19:30:14 -0400
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| X-RFC2646: Format=Flowed; Response
| Message-ID: <[email protected]>
| Newsgroups:
microsoft.public.dotnet.distributed_apps,microsoft.public.dotnet.framework,m
icrosoft.public.dotnet.languages.csharp
| NNTP-Posting-Host: 201.239.165.24.cfl.res.rr.com 24.165.239.201
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.dotnet.framework:29645
microsoft.public.dotnet.languages.csharp:110656
microsoft.public.dotnet.distributed_apps:3501
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| Find out if the Server produces an industry standard "WSDL" contract xml
| document. If it does, your job is much easier - you can create a SOAP
proxy
| class from the WSDL directly. Otherwise,
| you will need to create classes based on the SOAP Schema, and submit them
to
| the server as standard SOAP messages.
| Peter
|
| | >i need to develop a SOAP client, Since I have never personally done one
I
| >would like to make sure that I am going about it correctly.
| > The client is a Windows (probably 2k3) application that communicates
over
| > HTTPS SOAP. The remote server is Unix based and implements Axis, which
I
| > know nothing about
| >
| > What are the steps I need to create this client? I will be developing
in
| > C# and I have the XML schema of the SOAP messages.
| > How do I get started?
| > thanks for your help
| > m
| >
|
|
|
 
M

MR

.... and what do I do if they haven't published the WSDL document? they have
no plans to publish one in the foreseeable future

Steven Cheng said:
Thanks for Peter's informative suggestions.

Hi RM,

As Peter has mentioned, for consuming a certain XML WebServcice in our
clientside appolication, the most important is to get a copy of the
webservice's WSDL document since the WSDL is the contract of the
webservice
which define the type system and message format and service specific
infos.
I think the apache axis should has its own means to expose such
description. After you get it, we can use the WSDL.exe (or the
AddWebReference feature in VS.NET) to help generate the .net classes for
consuming the webservice. Anyway, I think we can start from this.

#Web Services Description Language Tool (Wsdl.exe)
http://msdn.microsoft.com/library/d...webservicesdescriptionlanguagetoolwsdlexe.asp

Hope also helps.

Steven Cheng
Microsoft Online Support

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




--------------------
| From: "Peter Bromberg [C# MVP]" <[email protected]>
| References: <[email protected]>
| Subject: Re: SOAP project
| Date: Sun, 17 Jul 2005 19:30:14 -0400
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| X-RFC2646: Format=Flowed; Response
| Message-ID: <[email protected]>
| Newsgroups:
microsoft.public.dotnet.distributed_apps,microsoft.public.dotnet.framework,m
icrosoft.public.dotnet.languages.csharp
| NNTP-Posting-Host: 201.239.165.24.cfl.res.rr.com 24.165.239.201
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.dotnet.framework:29645
microsoft.public.dotnet.languages.csharp:110656
microsoft.public.dotnet.distributed_apps:3501
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| Find out if the Server produces an industry standard "WSDL" contract xml
| document. If it does, your job is much easier - you can create a SOAP
proxy
| class from the WSDL directly. Otherwise,
| you will need to create classes based on the SOAP Schema, and submit
them
to
| the server as standard SOAP messages.
| Peter
|
| | >i need to develop a SOAP client, Since I have never personally done one
I
| >would like to make sure that I am going about it correctly.
| > The client is a Windows (probably 2k3) application that communicates
over
| > HTTPS SOAP. The remote server is Unix based and implements Axis, which
I
| > know nothing about
| >
| > What are the steps I need to create this client? I will be developing
in
| > C# and I have the XML schema of the SOAP messages.
| > How do I get started?
| > thanks for your help
| > m
| >
|
|
|
 
M

MR

i was given some DTDs. how do i generate the XML files based on these docs?

Steven Cheng said:
Thanks for Peter's informative suggestions.

Hi RM,

As Peter has mentioned, for consuming a certain XML WebServcice in our
clientside appolication, the most important is to get a copy of the
webservice's WSDL document since the WSDL is the contract of the
webservice
which define the type system and message format and service specific
infos.
I think the apache axis should has its own means to expose such
description. After you get it, we can use the WSDL.exe (or the
AddWebReference feature in VS.NET) to help generate the .net classes for
consuming the webservice. Anyway, I think we can start from this.

#Web Services Description Language Tool (Wsdl.exe)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/htm
l/cpgrfwebservicesdescriptionlanguagetoolwsdlexe.asp

Hope also helps.

Steven Cheng
Microsoft Online Support

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




--------------------
| From: "Peter Bromberg [C# MVP]" <[email protected]>
| References: <[email protected]>
| Subject: Re: SOAP project
| Date: Sun, 17 Jul 2005 19:30:14 -0400
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| X-RFC2646: Format=Flowed; Response
| Message-ID: <[email protected]>
| Newsgroups:
microsoft.public.dotnet.distributed_apps,microsoft.public.dotnet.framework,m
icrosoft.public.dotnet.languages.csharp
| NNTP-Posting-Host: 201.239.165.24.cfl.res.rr.com 24.165.239.201
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.dotnet.framework:29645
microsoft.public.dotnet.languages.csharp:110656
microsoft.public.dotnet.distributed_apps:3501
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| Find out if the Server produces an industry standard "WSDL" contract xml
| document. If it does, your job is much easier - you can create a SOAP
proxy
| class from the WSDL directly. Otherwise,
| you will need to create classes based on the SOAP Schema, and submit
them
to
| the server as standard SOAP messages.
| Peter
|
| | >i need to develop a SOAP client, Since I have never personally done one
I
| >would like to make sure that I am going about it correctly.
| > The client is a Windows (probably 2k3) application that communicates
over
| > HTTPS SOAP. The remote server is Unix based and implements Axis, which
I
| > know nothing about
| >
| > What are the steps I need to create this client? I will be developing
in
| > C# and I have the XML schema of the SOAP messages.
| > How do I get started?
| > thanks for your help
| > m
| >
|
|
|
 
S

Steven Cheng[MSFT]

Hi MR,

Thanks for your followup.
I'm afraid that would be very unprofessional if they don't provide a valid
and complete WSDL for their published webservice. The WSDL is the
fundamental service contract of the webservice, just like the IDL/type
library for COM.

#Understanding WSDL
http://msdn.microsoft.com/webservices/understanding/webservicebasics/default
..aspx?pull=/library/en-us/dnwebsrv/html/understandwsdl.asp

who are the service hoster, your own internal department, your partner or
..? Anyway, I strongly recommend that you contact with them on this since
WSDL is really necessary. If there're anything else we can help , please
feel free to post here.

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.)




--------------------
| From: "MR" <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
| Subject: Re: SOAP project
| Date: Wed, 20 Jul 2005 20:50:33 +0300
| Lines: 91
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.dotnet.languages.csharp
| NNTP-Posting-Host: hevron.biconix.com 62.90.12.234
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.languages.csharp:111306
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| ... and what do I do if they haven't published the WSDL document? they
have
| no plans to publish one in the foreseeable future
|
| | > Thanks for Peter's informative suggestions.
| >
| > Hi RM,
| >
| > As Peter has mentioned, for consuming a certain XML WebServcice in our
| > clientside appolication, the most important is to get a copy of the
| > webservice's WSDL document since the WSDL is the contract of the
| > webservice
| > which define the type system and message format and service specific
| > infos.
| > I think the apache axis should has its own means to expose such
| > description. After you get it, we can use the WSDL.exe (or the
| > AddWebReference feature in VS.NET) to help generate the .net classes for
| > consuming the webservice. Anyway, I think we can start from this.
| >
| > #Web Services Description Language Tool (Wsdl.exe)
| >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/htm
l/cpgrfwebservicesdescriptionlanguagetoolwsdlexe.asp
| >
| > Hope also helps.
| >
| > Steven Cheng
| > Microsoft Online Support
| >
| > Get Secure! www.microsoft.com/security
| > (This posting is provided "AS IS", with no warranties, and confers no
| > rights.)
| >
| >
| >
| >
| > --------------------
| > | From: "Peter Bromberg [C# MVP]" <[email protected]>
| > | References: <[email protected]>
| > | Subject: Re: SOAP project
| > | Date: Sun, 17 Jul 2005 19:30:14 -0400
| > | Lines: 23
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| > | X-RFC2646: Format=Flowed; Response
| > | Message-ID: <[email protected]>
| > | Newsgroups:
| >
microsoft.public.dotnet.distributed_apps,microsoft.public.dotnet.framework,m
| > icrosoft.public.dotnet.languages.csharp
| > | NNTP-Posting-Host: 201.239.165.24.cfl.res.rr.com 24.165.239.201
| > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.dotnet.framework:29645
| > microsoft.public.dotnet.languages.csharp:110656
| > microsoft.public.dotnet.distributed_apps:3501
| > | X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
| > |
| > | Find out if the Server produces an industry standard "WSDL" contract
xml
| > | document. If it does, your job is much easier - you can create a SOAP
| > proxy
| > | class from the WSDL directly. Otherwise,
| > | you will need to create classes based on the SOAP Schema, and submit
| > them
| > to
| > | the server as standard SOAP messages.
| > | Peter
| > |
| > | | > | >i need to develop a SOAP client, Since I have never personally done
one
| > I
| > | >would like to make sure that I am going about it correctly.
| > | > The client is a Windows (probably 2k3) application that communicates
| > over
| > | > HTTPS SOAP. The remote server is Unix based and implements Axis,
which
| > I
| > | > know nothing about
| > | >
| > | > What are the steps I need to create this client? I will be
developing
| > in
| > | > C# and I have the XML schema of the SOAP messages.
| > | > How do I get started?
| > | > thanks for your help
| > | > m
| > | >
| > |
| > |
| > |
| >
|
|
|
 
W

Wessel Troost

I'm afraid that would be very unprofessional if they don't provide a
valid
and complete WSDL for their published webservice. The WSDL is the
fundamental service contract of the webservice, just like the IDL/type
library for COM.
We regularly do not get WSDL here. In some SOAP implementations, the WSDL
is not generated automatically, and it's pretty tough to ask someone to
make their own WSDL.

What I do get are examples and sometimes a DTD/XML Schema.

Then I call the SOAP service like this:

HttpWebRequest req =
(HttpWebRequest)WebRequest.Create("http://yoururl");
req.Headers.Add("SOAPAction","\"\"");
req.ContentType = "text/xml;charset=\"utf-8\"";
req.Accept = "text/xml";
req.Method = "POST";
writer = new StreamWriter( req.GetRequestStream() );
writer.Write( "your SOAP document here" );
writer.Close();
WebResponse resp = req.GetResponse();
Stream stm = resp.GetResponseStream();
StreamReader r = new StreamReader(stm);
string sSOAPAnswer = r.ReadToEnd();

The SOAP document is based on the example document. The answer is parsed
using the XML parser.

Greetings,
Wessel
 
S

Steven Cheng[MSFT]

Hi Wessel,

Thanks for your further response. If it's really hard to get the WSDL, the
means you currently used (through httpwebrequest and manually generate soap
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 less
error-prone. Here are some msdn reference on the xsd.exe tool and Xml
Serialization in .NET:

#XML Schema Definition Tool (Xsd.exe)
http://msdn.microsoft.com/library/en-us/cptools/html/cpconxmlschemadefinitio
ntoolxsdexe.asp?frame=true

#XML and SOAP Serialization
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconserialization.asp?
frame=true

Hope 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.)





--------------------
| Subject: Re: SOAP project
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
| Message-ID: <op.st9aodk4f3yrl7@asbel>
| Date: Thu, 21 Jul 2005 11:15:39 +0200
| From: "Wessel Troost" <[email protected]>
| Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
| MIME-Version: 1.0
| Content-Transfer-Encoding: 8bit
| 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!TK2MSFTNGP15.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.languages.csharp:111433
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| > I'm afraid that would be very unprofessional if they don't provide a
| > valid
| > and complete WSDL for their published webservice. The WSDL is the
| > fundamental service contract of the webservice, just like the IDL/type
| > library for COM.
| >
| We regularly do not get WSDL here. In some SOAP implementations, the
WSDL
| is not generated automatically, and it's pretty tough to ask someone to
| make their own WSDL.
|
| What I do get are examples and sometimes a DTD/XML Schema.
|
| Then I call the SOAP service like this:
|
| HttpWebRequest req =
| (HttpWebRequest)WebRequest.Create("http://yoururl");
| req.Headers.Add("SOAPAction","\"\"");
| req.ContentType = "text/xml;charset=\"utf-8\"";
| req.Accept = "text/xml";
| req.Method = "POST";
| writer = new StreamWriter( req.GetRequestStream() );
| writer.Write( "your SOAP document here" );
| writer.Close();
| WebResponse resp = req.GetResponse();
| Stream stm = resp.GetResponseStream();
| StreamReader r = new StreamReader(stm);
| string sSOAPAnswer = r.ReadToEnd();
|
| The SOAP document is based on the example document. The answer is parsed

| using the XML parser.
|
| Greetings,
| Wessel
|
 
W

Wessel Troost

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
 
S

Steven Cheng[MSFT]

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: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]> <op.st9aodk4f3yrl7@asbel>
<[email protected]>
| From: "Wessel Troost" <[email protected]>
| 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
|
 
W

Wessel Troost

As for those webservice which doesn't interop well between different
client/server, it is often caused by the message contract not well
defined.

The interop problems I've seen are between .NET and AXIS, an open source
tool:
http://ws.apache.org/axis/

It may be that AXIS is in error, but you can't expect the business
developers of the other party to fix AXIS.

There's another Web Service written in perl. They parse the incoming
"SOAP" calls by hand. Of course, there is no WSDL for that.
Thanks for the pointer, interesting read! Although I think the author's
suggestion to write XML Schema using notepad may not be feasable for
small-sized projects. Say you have a week or two for the development of a
Web Service. Handcoding XML Schema's would take a large chunk of an
already tight schedule.

Greetings,
Wessel
 
S

Steven Cheng[MSFT]

Yes, sometimes limited to the specific condition, I could not but use some
informal means. However, if possible , providing WSDL is always the
prefered and recommended thing. Anyway, if there are any other questions
later, please feel free to post here.

Thanks & Regards,

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: Mon, 25 Jul 2005 08:06:22 +0200
| Subject: Re: SOAP project
| References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]> <op.st9aodk4f3yrl7@asbel>
<[email protected]> <op.sua1hto1f3yrl7@asbel>
<[email protected]>
| From: "Wessel Troost" <[email protected]>
| Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
| MIME-Version: 1.0
| Content-Transfer-Encoding: 8bit
| Message-ID: <op.suggkw1mf3yrl7@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!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.languages.csharp:111960
| X-Tomcat-NG: microsoft.public.dotnet.languages.csharp
|
| > As for those webservice which doesn't interop well between different
| > client/server, it is often caused by the message contract not well
| > defined.
|
| The interop problems I've seen are between .NET and AXIS, an open source
| tool:
| http://ws.apache.org/axis/
|
| It may be that AXIS is in error, but you can't expect the business
| developers of the other party to fix AXIS.
|
| There's another Web Service written in perl. They parse the incoming
| "SOAP" calls by hand. Of course, there is no WSDL for that.
|
| > #Contract-First Service Development
| >
http://msdn.microsoft.com/msdnmag/issues/05/05/ServiceStation/default.aspx
| >
| Thanks for the pointer, interesting read! Although I think the author's
| suggestion to write XML Schema using notepad may not be feasable for
| small-sized projects. Say you have a week or two for the development of
a
| Web Service. Handcoding XML Schema's would take a large chunk of an
| already tight schedule.
|
| Greetings,
| Wessel
|
 
J

j-integra_support

If tight schedules are a concern, you may want to use an
interoperability tool such as J-Integra Espresso instead of Web
Services. Many people are choosing software "bridges" because Web
Services (a) are too complicated to setup quickly and (b) are too slow
for their requirements. The nice thing is that you can still develop in
C# (or whatever .NET language you are comfortable with) - the J-Integra
Espresso tools will do all the setup and configuration for you!

Shane Sauer
J-Integra Interoperability Solutions
http://j-integra.intrinsyc.com/
When Web Services are not enough
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top