hi Adel If u look at the WSDL the ConvertTemperature element is supposed to have a child called dFarenheit. But the child ( of ConvertTemperature) in the SOAP request is op1. I believe this can cause a problem. The other thing that you might want to take a look at would be the fact that the ConvertTemparature doesnt have an xsi:type and also the fact that there is no namepace mapped to xmlns( ie. without a prefix) . Since in your case it is an anonymous type i dont know how it would be. But i have seen .net fail when there is no proper xsi:type attributes in the xml Hope this helps. Vidyanand
-----Original Message----- From: Adel Habib [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 28, 2002 5:54 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Help Help Help - Axis client to .Net Service problem For some reason, the parameters I send from an Axis' client does not reach the .Net Service (the Service behaves as if the value of the params is zero). this is a simple Service that returns the Celsius value of a Fahrenheit input. Do you see anything wrong with my Java Client file. I am using Axis-Beta1 Here is Details:
