Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>While I am a java proponent and have little C# experience, I will honestly say they will likely be about equal, and you should go with whatever language you are most familiar with and comfortable in programming.</p> <p>On the Java side, both exposing and consuming web services (SOAP or REST) can be easily done via open source libraries (and there may even be some stuff built into the JDK at this point, although usually they are a bit behind the open source community), one of the most popular being Spring. This will do for you all the complexity and plumbing around creating and consuming SOAP, and exposing or consuming REST.</p> <p>For SOAP:</p> <p>For REST:</p> <p><a href="http://blog.springsource.com/2009/03/08/rest-in-spring-3-mvc/" rel="nofollow noreferrer">http://blog.springsource.com/2009/03/08/rest-in-spring-3-mvc/</a></p> <p><a href="http://blog.springsource.com/2009/03/27/rest-in-spring-3-resttemplate/" rel="nofollow noreferrer">http://blog.springsource.com/2009/03/27/rest-in-spring-3-resttemplate/</a></p> <p>For SOAP:</p> <p><a href="http://static.springsource.org/spring-ws/sites/1.5/" rel="nofollow noreferrer">http://static.springsource.org/spring-ws/sites/1.5/</a></p> <p>Note Spring is just one option (but a good one), but my overall point is don't write the plumbing yourself, choose an existing framework to do it for you and it shouldn't matter what language you use. </p> <p>As mentioned I don't know much about C# but what I've found is they usually take the good parts of the core JDK and the open source java community and build it into the language, so there may be some nice native stuff in C# that mirrors what Spring has done for Java.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload