Soap calls appear to be broken?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. service stack examples project
2. make any soap call
3. all xml and rest calls still seem to work

What is the expected output? What do you see instead?
The message with To 'http://<hostname>/Public/Soap11/SyncReply.svc/<service>' 
cannot be processed at the receiver, due to an AddressFilter mismatch at the 
EndpointDispatcher.  Check that the sender and receiver's EndpointAddresses 
agree

What version of the product are you using? On what operating system?
latest on windows 7. some chatter on the web suggests a .net framework patch 
may be to blame?

Please provide any additional information below.

Original issue reported on code.google.com by LepardUK on 20 Oct 2010 at 7:52

[GoogleCodeExporter]

Hi Leopard,

In order to get the 'Add Service Reference' code generation to work, I've 
tweaked the types namespace in the WSDL schema from:

http://www.servicestack.net/types/
to:
http://www.servicestack.net/types

The latest example project (v1.57) includes a code generated proxy created by 
VS.NET when looking at the SOAP 1.2 WSDL - Which you can get here:
http://servicestack.googlecode.com/files/ServiceStack.Examples-v1.57.zip

Let me know if this fixes your issue as well.

Cheers,
- Demis

Original comment by demis.be...@gmail.com on 24 Oct 2010 at 11:45

[GoogleCodeExporter]

Soap12 wsdl is still invalid in places according to the validation tool I am 
using, which causes knock on efects when consuming the service. The namespace 
defined is "soap12" but several of the operations are defined in "soap". I can 
obviously fix this manually and save to a file, but when you get a chance it 
would be nice to have this fixed.

Original comment by LepardUK on 25 Oct 2010 at 7:27

[GoogleCodeExporter]

Hi Leopard,

I apologize for the delay, as I've only now managed to find the time to look 
into the issue again. 
It looks like that I broke the SOAP endpoints during my last big re-factor. 
Anyway the issues should be resolved now and I've added some tests in 
ServiceStack as well as a couple of test pages that calls the Example 
ServiceStack Web Services here:

http://www.servicestack.net/ServiceStack.Examples.Clients/Soap11.aspx
http://www.servicestack.net/ServiceStack.Examples.Clients/Soap12.aspx

The example pages use the generated proxies created by VS.NET's 'Add Service 
Reference'

Source code:
https://github.com/mythz/ServiceStack.Examples/blob/master/src/ServiceStack.Exam
ples.Clients/Soap11.aspx.cs
https://github.com/mythz/ServiceStack.Examples/blob/master/src/ServiceStack.Exam
ples.Clients/Soap12.aspx.cs

Note: The live demo is running on Mono and historically their support for WCF 
has been poor although having just upgraded to 2.8 last night it appears to 
work ok. Unfortunately they still have a buggy XmlSchema implementation so 
generating the WSDL doesn't work at the moment but works fine on windows. FYI 
the prefix has changed from '/Public' to '/ServiceStack' and now the Web.config 
is a lot cleaner with only one httpHanlder mapping required and all the WCF 
configuration removed. The new location for the WSDL is now at the following 
locations:

http://localhost/ServiceStack.Examples.Host.Web/ServiceStack/Soap11
http://localhost/ServiceStack.Examples.Host.Web/ServiceStack/Soap12

Anyway the new Example project is available at:
https://github.com/downloads/mythz/ServiceStack.Examples/ServiceStack.Examples-v
1.63.zip

Let me know if the latest builds resolve your problems.

Cheers,
- Demis

Original comment by demis.be...@gmail.com on 4 Dec 2010 at 6:17