Comments on: Building webservices with Spring.Net http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/ .net developer with a touch of Cocoa Sat, 03 Dec 2011 15:56:05 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Benny Michielsen http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/#comment-25 Benny Michielsen Wed, 14 Oct 2009 19:14:55 +0000 /post/2008/07/21/Building-webservices-with-SpringNet.aspx#comment-25 Thanks for the heads up! Thanks for the heads up!

]]> By: Bruno Baia http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/#comment-24 Bruno Baia Wed, 14 Oct 2009 17:10:41 +0000 /post/2008/07/21/Building-webservices-with-SpringNet.aspx#comment-24 Hi, This is a .NET Framework bug, not related to Spring.NET. http://forum.springframework.net/showthread.php?p=15390 Cheers, Bruno Baia Hi,

This is a .NET Framework bug, not related to Spring.NET.
http://forum.springframework.net/showthread.php?p=15390

Cheers,
Bruno Baia

]]> By: Angga Lingga http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/#comment-23 Angga Lingga Wed, 10 Jun 2009 10:36:51 +0000 /post/2008/07/21/Building-webservices-with-SpringNet.aspx#comment-23 Thanks for the explanation for creating webservice with spring .net. It has helped me to finished my job. Thank you very much ... :D Thanks for the explanation for creating webservice with spring .net. It has helped me to finished my job. Thank you very much … :D

]]> By: TBRays http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/#comment-22 TBRays Thu, 16 Apr 2009 14:20:20 +0000 /post/2008/07/21/Building-webservices-with-SpringNet.aspx#comment-22 Thanks for taking your time to look into this. I will follow the the thread on the forum. Thanks for taking your time to look into this. I will follow the the thread on the forum.

]]> By: Benny Michielsen http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/#comment-21 Benny Michielsen Wed, 15 Apr 2009 20:36:49 +0000 /post/2008/07/21/Building-webservices-with-SpringNet.aspx#comment-21 Created a topic, http://forum.springframework.net/showthread.php?p=15390#post15390 best to follow there. Created a topic, http://forum.springframework.net/showthread.php?p=15390#post15390 best to follow there.

]]> By: Benny Michielsen http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/#comment-20 Benny Michielsen Wed, 15 Apr 2009 20:23:56 +0000 /post/2008/07/21/Building-webservices-with-SpringNet.aspx#comment-20 Odd indeed, I was able to reproduce this immediately on my virtual machine. Very strange because I've developed several applications over the past years using this approach and never ran into this. While I've been able to reproduce the exception I haven't found a solution yet. I've update my VM to SP1, set the host for 3.5, introduced classes, moved them around, deleted temp asp.net stuff, etc etc . The problem remains. What is even more bizarre is that if you add a parameter to one of the methods in the sample there's no problem. Remove that parameter, no problem. Introduce a new method, no problem. Change that method, no problem. Remove the new method, no problem. In the end, somehow, I did get the service to work when changing the parameter on one of the original methods but I was unable to trace my steps back. I'm going to create a topic on the Spring forum and will post the link here. Odd indeed, I was able to reproduce this immediately on my virtual machine. Very strange because I’ve developed several applications over the past years using this approach and never ran into this.

While I’ve been able to reproduce the exception I haven’t found a solution yet. I’ve update my VM to SP1, set the host for 3.5, introduced classes, moved them around, deleted temp asp.net stuff, etc etc . The problem remains.

What is even more bizarre is that if you add a parameter to one of the methods in the sample there’s no problem. Remove that parameter, no problem. Introduce a new method, no problem. Change that method, no problem. Remove the new method, no problem.

In the end, somehow, I did get the service to work when changing the parameter on one of the original methods but I was unable to trace my steps back. I’m going to create a topic on the Spring forum and will post the link here.

]]> By: TBRays http://blog.bennymichielsen.be/2008/07/21/building-webservices-with-spring-net/#comment-19 TBRays Wed, 15 Apr 2009 15:48:12 +0000 /post/2008/07/21/Building-webservices-with-SpringNet.aspx#comment-19 First thanks for posting this example it has been very helpful. There is one bit of oddity that maybe you can clear up though. While goofing around with your example I noticed that any change to method signatures or even adding a new method to the service causes problems even if the changes build correctly. For example let's say we change the SearchProductsResponse method to accept a string as the parameter. All reference are updated as well and we also restart the web server to be thorough. Without fail we get: "The XML element 'SearchProductsResponse' from namespace 'http://Just/testing' references a method and a type. Change the method's message name using WebMethodAttribute or change the type's root element using the XmlRootAttribute." Our research indicates this comes from a generated WSDL that is out of sync with the service changes. Kinda odd when there is no wsdl hanging around. Do you have any insight on what could be going on here? Thanks First thanks for posting this example it has been very helpful.

There is one bit of oddity that maybe you can clear up though. While goofing around with your example I noticed that any change to method signatures or even adding a new method to the service causes problems even if the changes build correctly.

For example let’s say we change the SearchProductsResponse method to accept a string as the parameter. All reference are updated as well and we also restart the web server to be thorough.

Without fail we get:
“The XML element ‘SearchProductsResponse’ from namespace ‘http://Just/testing‘ references a method and a type. Change the method’s message name using WebMethodAttribute or change the type’s root element using the XmlRootAttribute.”

Our research indicates this comes from a generated WSDL that is out of sync with the service changes. Kinda odd when there is no wsdl hanging around. Do you have any insight on what could be going on here?

Thanks

]]>