Re: Hitting an ASP.NET webservice with a java client.

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Thu, 23 Jun 2005 07:36:11 -0700

There is noway to get a JAX-RPC client to change this behavior without a
patch to the code.
However, JAX-WS 2.0 EA2 (JAX-WS is the next generation of web services)
was just release on
yesterday. I believe it will work for your. You can download EA2 at:

David Sharp wrote:

> I'm having problems hitting an ASP.NET <> web service I
> have created with a java client. I'm currently trying to determine if
> the problem is with the web service, or with the client. The client
> is blowing up with the following error:
> expected element is missing: {uri:ClaimNet-types}Question
> However the soap message being returned *has* the Question element in
> the proper place:
> <?xml version=" 1.0" encoding="utf-8"?>
> <soap:Envelope xmlns:xsi=""
> xmlns:xsd=""
> xmlns:soap=""
> <>>
> <soap:Body>
> <getSecurityQuestion-return xmlns="uri:ClaimNet-types">
> <Question>
> <Display>Why?</Display>
> <Answer>Because</Answer>
> </Question>
> <Question>
> <Display>How?< /Display>
> <Answer>Somehow</Answer>
> </Question>
> </getSecurityQuestion-return>
> </soap:Body>
> </soap:Envelope>
> jax-rpc (using jwsdp-1.5) appears to be parsing this message
> incorrectly (it thinks Question has no namespace).
> makes it pretty clear
> that the default namespace declared in "getSecurityQuestion-return"
> should apply to its children as well. Is there a way to make it do
> the right thing?
> Thanks,
> Dave

 - Doug