The Java web service has been changed to Document/literal. So know, I just
generate the proxy class with wsdl.exe and try to call the web method. The
problem remains the same, so it is not a Document/RPC problem, but a code
problem. Heres my code:
{
javaService js = new javaService();
testMethod vReq = new testMethod();
vReq.param1 = 1;
reponseWS info = null;
info = js.testMethod(vReq);
int state = info.result;
if (state = = 0) return false;
else return true;
}
javaService is the class that represents the web service, testMethod is the
class that represents the web method and reponseWS is the class that
represents the web method return value. All this classes are generated by
wsdl.exe.
Although I inspect the SOAP reponse, and I can see "result"'s value is 1,
the content of the "info" object is not the correct one. It's always 0, as
if it's not even initialized.
Maybe all this doesn' work the way I'm trying to do it.
Anyone??
Rafa Llarena
> Hi,
>
[quoted text clipped - 32 lines]
>
> Rafa Llarena
Rafa Llarena - 28 Apr 2005 09:52 GMT
I've kept researching and I've arrived to the conclusion that the problem
maybe in the return value of the web method. It returns a struct, and .NET
seems to have a problem retrieving this struct. Am I wrong here? Is there
anything I have to do when the web method's return type is a structure?
If anyone has a clue, please, answer
Rafa
> The Java web service has been changed to Document/literal. So know, I just
> generate the proxy class with wsdl.exe and try to call the web method. The
[quoted text clipped - 63 lines]
>>
>> Rafa Llarena
Brock Allen - 28 Apr 2005 13:44 GMT
It's possible that the Java WebService is defined using WSDL and XSD that
the .NET framework can't consume automatically. You might have to work with
the XML message directly in your client.
-Brock
DevelopMentor
http://staff.develop.com/ballen
> I've kept researching and I've arrived to the conclusion that the
> problem
[quoted text clipped - 80 lines]
>>> I hope I've explained myself properly.
>>> Rafa Llarena
Rafa Llarena - 29 Apr 2005 11:44 GMT
Thank you very much for your answer.
Is there any way to find out if that's actually the problem?
Rafa Llarena
> It's possible that the Java WebService is defined using WSDL and XSD that
> the .NET framework can't consume automatically. You might have to work
[quoted text clipped - 88 lines]
>>>> I hope I've explained myself properly.
>>>> Rafa Llarena