This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Hi all. I know who to create and use a web service in Java. writting the server end point interface and its implementation, then using wscompile tool to generate WSDL file and the static stubs. consider the following situation : we have a .NET web service in the server, and the client will be a Java client using JAX-RPC API, static stubs. some code :
well, I just need some explainations... 1. how my Java client will get its static stub of .NET service ? 2. how my Java client will get all the available methods of the service ? I know it is the mission of WSDL file, but I am not sure how.. more easily : How to access a .NET web serivce in Java client ? would you mind telling me the required steps ?? thanks for help. [ January 14, 2005: Message edited by: John Todd ]
from the apache axis point of view. WDSL2Java tool will take care of all the steps and requirements... Basically it will generate all the neccessary stubs code to access any methods listed under a wsdl file. All u have to do is make use of that stub classes. Guess i answered ur question... if not plz comment back.
Thanks. please correct me if I'm wrong. we have a web service developed using .net, the URL of this service is : http://.netservice/ws/catalog.asmx (or what ever). so to access this service in a Java client, we perform : 1. get the WSDL file of this .net service. 2. using wscompile tool (in case we are using SJSAS) to generate the static stubs. 3. done. now we can use these static stubs to access the web service, right ??
The biggest challenge in getting your client to go cross-platform is getting your hands on the WSDL. I just came from the other direction, trying to connect my .NET client to a Java Web Service. My biggest difficulty was trying to figure out the URL to supply for the service, which meant understanding the App Server's organizational/jar structure and puzzling out the DD's. It's much worse puzzling out .NET client/Java Web Service than Java client/.NET service.
Neither one's particularly difficult, though, once you have your hands on the URL to the service.
Once I found the URL on which to append my "?WSDL" the rest was dead easy proxy boilerplating. It should be for you too.
When you're a Java client trying to find the WSDL for the .NET service, you need to have the URL and the service ".asmx" file. With .NET, the URL is always a physical path straight to the physical ".asmx" file. There's no DD-based indirection like there is in Java.