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
