Just to add to Anne's comment RE: .NET If you are going to be exposing your web service for consumption by varied clients, it may be worthwhile to consider the WSDL/Schema first approach to implementing your web service and client piece.
In short: - Define the messages that are going to be exchanged between the client the service in a message schema (XSD file) - Generate a WS-I compliant WSDL from the message Schema - On the Service side use WSDL2Java to create your service stub and do the implementation. - On the client side, in addition to what Anne mentioned, another option is to use the free WSCF tool that will generate the client proxies in .NET from the schema and the WSDL. You can find it @ http://www.thinktecture.com/Resources/Software/WSContractFirst/default.h tml One of the added benefits with this tool is that you have the ability to automate the creation of the WSDL from the Message Schema using this tool. The generated WSDL is WS-I BP 1.1 compliant. Hand creating/editing WSDL is not for the faint of heart :-) A drawback is that the GUI version of the tool is a VS.NET add-in, which means that it needs to be installed under Visual Studio.NET. But there is also a command line version of the tool available. This BTW, does NOT guarantee InterOp, it just improves your chance of success! In particular, the things to watch out for would be the lack of schema artifact support in the tools that are doing the Schema-to-Code Mapping e.g. Lack of support for the <choice> artifact under JAX-RPC or Lack of support for Substitution groups under .NET. You can maximize your chance of a successful InterOp by focusing keeping things simple. Regards, - Anil -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Saturday, June 04, 2005 5:56 PM To: [email protected] Subject: Re: Calling Axis WebServices from C and .NET When consuming a web service from .NET, you should use the .NET WebReference client capability. (Simply add a WebReference to your client application.) It's not good idea to use an unmanaged code implementation, such as Axis C++. For C/C++ applications on Linux, you can use Axis C++ or gSOAP (http://www.cs.fsu.edu/~engelen/soap.html) or a commerical implementation such as Systinet Server for C++ (http://www.systinet.com/products/ssc/overview). For old ASP apps, if they are written in VB6, I suggest that you use PocketSOAP (http://www.pocketsoap.com). If these apps are written in C/C++ then you could use either PocketSOAP or any of the three C/C++ tools. Anne On 6/4/05, Leslie Tighe <[EMAIL PROTECTED]> wrote: > Hello, > > I have a set of java components in a J2EE app that I need to expose as > a webservice. I was planning on using Axis 1.2 for this. However, the > client layer can be quite varied - C application on Linux, .NET > applications and old ASP apps. Can any suggest how to best approach > the client part of this and what tools should I be using? I am > assuming that for the .NET app, I can consume the J2EE services using > the C++ version of Axis, but I am not sure about the others. > > Thanks in advance for your help. > > Regards > Leslie > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com
