Re: Reading a Java webservice with VB.NET

From: JL (jlaugesen_at_yahoo.com)
Date: 04/23/04 

Date: 23 Apr 2004 06:23:41 -0700

Hello Dino and Newsgroup.

I have solved this problem and thought I'd post a summary of what
happened in case it can help someone else.

My client created a very simple "Hello World" web service. Call a
method, get "Hello World" back as a string. Using VB.NET's web
reference I was unable to connect to the web service. Then I used
wsdl.exe on the URL for the wsld (web service's url + "?wsdl" and a
"/l:vb" flag) and it created a .vb file. I put it in the VB.NET
program and it worked.

Using the wsdl.exe program on the actual wsdl still did not work. It
returned an error that it was unable to bind with one of the methods.
So I downloaded a text copy of the wsdl, delete that one method, and
ran wsdl.exe on the text wsdl file again. It said it could not bind
with another method. Deleted it too. Kept going and deleted 7 of the
18 methods, and then it worked.

The one thing that was common with the 7 deleted ones that didn't
exist in all the others was a specific datatype. The web service was
rebuilt eliminating that datatype and it worked.

JL

"Dino Chiesa [Microsoft]" <dinoch@online.microsoft.com> wrote in message news:<ew1PDVKKEHA.644@tk2msftngp13.phx.gbl>...
> When you say "Java web services" - what Java stackdoes the system use?
> you mentioned an Apache server, but if you are referring to Apache HTTPD,
> that doesn't make a whole lot of difference here.
>
> There are at least 5 different Java-based webservices stacks. They all
> behave differently. Some of them are more interoperable with .NET than
> others. some of them are more compliant to the WS-I standards than others.
>
> The IBM webservices tookit (WSDK v5.1 I suppose) includes one of the web
> services runtimes. But, if you already have your webservices running, then
> I don't know what you'll use WSDK v5.1 for.
>
> A good place to start is to trace the HTTP traffic going to and from the
> server. do it with a Java client, then compare your results to what you get
> with a .NET client. Note the differences. There are a couple of tools that
> can do this. Apache AXIS includes an HTTP tracing tool (a redirector).
> Simon Fell has a proxytrace tool that is nice but not all Java stacks can
> use it.
>
>
> Also - can you post the WSDL you are using?
>
>
> -Dino
>

Relevant Pages

  • Re: WSDL.exe vs. "Add Web Reference"
    ... For example this complexType: ... I them created a WSDL using the XSD. ... Then I placed this file in an "Empty Web Project", added a Web Service, made ... If I do all these steps correctly the client should ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Differences in WSDL between versions of a web service.
    ... Never change the signature of an already released method in a webservice ... It doesn`t mather that your current WSDL is different as before, ... > what effect it might have on my client apps. ... > The original verison's WSDL contains sections for each web service ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: C# Web Services - usage by non .net clients?
    ... the only thing you need is the WSDL. ... your web service must conform to the WS-I BSP profile if others ... what if I develop a client in delphi or progress or Java? ... Would it be a client specific format of the Proxy class? ...
    (microsoft.public.dotnet.framework.webservices)
  • How do you transparently implement the same web service (WSDL) with java axis and .NET ?
    ... When I have tried to generate java and C# servers/clients from the same ... WSDL as described further below, these are the results I have been able ... When I try to invoke a C# web service with a java axis client I get the ... ..NET that are supporting the same WSDL and to be able to reuse client ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Implementing a common SOAP Header across multiple Web Service Pages
    ... to set a client up to reference multiple Web ... the Web Service site would ... Your point about leaving the ASMX page as lean as possible and acting just ...
    (microsoft.public.dotnet.framework.webservices)
Loading