«

I am calling a client's Java/Axis web service (I have no control over it's
code). I added the WSDL no problem. When I call their method, I get an
error:

Unhandled Exception: System.InvalidOperationException: There is an error in
XML document (13, 26). ---> System.InvalidCastException: Cannot assign
object of type System.Object[] to an object of type
ClientService.ClientElement[].

I see from the C# generated web service code on my end that this occurs
while generating the object returned via the web service. Any ideas of how
to go about tracking down how to fix this?

Amil

Take a look at the wsdl generated and the actual soap response
returned. It seems that the wsdl is defining a class as
ClientService.ClientElement[], but the response from the web service is
of type Object[]. This is not the first time I have seen these kind of
issues involving java web services being consumed by a .Net client. So
look at those two you might be able to tweak the wsdl, but I must admit
I am nto a java expert so i don't know.

OK, unfortunately I fixed the problem...by manually changing the
auto-generated WSDL code on my end from a ClientElement[] to an object[].
I'll try to figure out if .NET was doing something wrong.

Amil

"Keenan Newton" <> wrote in message
news: oups.com...
> Take a look at the wsdl generated and the actual soap response
> returned. It seems that the wsdl is defining a class as
> ClientService.ClientElement[], but the response from the web service is
> of type Object[]. This is not the first time I have seen these kind of
> issues involving java web services being consumed by a .Net client. So
> look at those two you might be able to tweak the wsdl, but I must admit
> I am nto a java expert so i don't know.
>

you'll want to look at the network trace to see what is being sent back and
forth.


"Amil" <> wrote in message
news:%23qr$...
> OK, unfortunately I fixed the problem...by manually changing the
> auto-generated WSDL code on my end from a ClientElement[] to an object[].
> I'll try to figure out if .NET was doing something wrong.
>
> Amil
>
> "Keenan Newton" <> wrote in message
> news: oups.com...
>> Take a look at the wsdl generated and the actual soap response
>> returned. It seems that the wsdl is defining a class as
>> ClientService.ClientElement[], but the response from the web service is
>> of type Object[]. This is not the first time I have seen these kind of
>> issues involving java web services being consumed by a .Net client. So
>> look at those two you might be able to tweak the wsdl, but I must admit
>> I am nto a java expert so i don't know.
>>
>
>