Bug 322400 (MONO79697)

---- Reported by spielc@gmx.at 2006-10-19 11:31:07 MST ----

Description of Problem:

Something seems to be terribly wrong with the current client-side soap
implementation of mono. I can develop the ws itself just fine, it compiles
well. i can even test it with xsp2 (using the web-service testbench xsp2
provides) BUT as soon as i try to actually USE it everything fails (on the
mono-side, i created a ws-proxy with axis-1.4 for my simple service and the
java-client works as expected). To be correct when i try to use the client
with the web-browser through a http-get-request i get the correct result
but when i try to use the by xsp2 automatically created test form (and thus
the SOAP-Execution), execution fails (the error msg the form displays is:
Error getting response stream (ReadDone2): ReceiveFailure). When i try to
use wsdl2 to create a local-proxy for the same web-service it creates the
cs-file with the code. it compiles fine but when i try to actually use the
proxy to execute the web-method of my service it fails again...

I think that it is a general problem because i experience this problem both
with a compiled 64-bit version on gentoo linux and with a binary 32-bit
windows-version.

Steps to reproduce the problem:
1. Create a web-service
2. Create a proxy for this web-service with the mono wsdl-to-c# tools
3. Compile the created file and execute it

Actual Results:

Web-Service-Proxy crashes.

Expected Results:

Web-Service-Proxy shouldn't crash and result should be displayed


How often does this happen? 

Always

Additional Information:

As said before problems occur on both compiled/binary 32-/62-bit
windows/linux verions of mono (tried both version 1.1.17 and 1.1.18 on
gentoo linux and the version 1.1.18 on windows)



---- Additional Comments From spielc@gmx.at 2006-10-20 14:48:23 MST ----

Okey after doing some more testing i have to say that i'm dumbfound. I
used the wsdl2-tool to create proxy's for two more web-services that
could be found on xmethods.com (the wsdl-files i used can be found
here: http://www.bs-byg.dk/hashclass.wsdl and
http://www.atomic-x.com/xmlservices/GuitarManufWS.asmx?wsdl). Both
proxy's worked well (except the fact that wsdl2 creates two completely
exact proxy's, which causes gmcs to choke on the file but as soon as
you comment the second class out everything works as expected... I'll
attach one of the generated cs-files to this bugreport)

Thus the problem seems to be related to the simple web-service i
implemented (the only thing i find kinda disturbing is the fact that
my ws works without any problems with the axis-client but i have no
chance to make it work with the c#-client.

I'll attach both the source-files of the web-service and the
c#-proxy-classfiles to this bug-report. Maybe somebody else can have a
look at it and has a hint what could be wrong!

Regards! 



---- Additional Comments From spielc@gmx.at 2006-10-20 14:53:40 MST ----

Created an attachment (id=170676)
c#-ws-proxy for http://www.atomic-x.com/xmlservices/GuitarManufWS.asmx?wsdl




---- Additional Comments From spielc@gmx.at 2006-10-20 14:56:27 MST ----

Created an attachment (id=170677)
c#-proxy for my sample ws




---- Additional Comments From spielc@gmx.at 2006-10-20 14:57:10 MST ----

Created an attachment (id=170678)
asmx-file of my web-service




---- Additional Comments From spielc@gmx.at 2006-10-20 14:59:28 MST ----

Created an attachment (id=170679)
implementation of this simple web-service


Imported an attachment (id=170676)
Imported an attachment (id=170677)
Imported an attachment (id=170678)
Imported an attachment (id=170679)

Unknown bug field "cf_op_sys_details" encountered while moving bug
   <cf_op_sys_details>Gentoo Linux-2006.1</cf_op_sys_details>