The .NET SOAP environment or the MS SOAP Toolkit correspond to Apache SOAP. They are SOAP runtime servers. (The tools that generate SOAP client proxies and SOAP server interfaces are tied to the SOAP runtime servers.) The Apache SOAP runtime runs as a servlet, therefore it requires a servlet engine to run. You can deploy the Apache SOAP runtime in almost any servlet engine (Tomcat, Jetty, JRun, WebLogic, WebSphere, Resin, etc.) Some servlet engines include an HTTP engine (e.g., Jetty, WebLogic). Others don't (e.g., Tomcat, JBoss). If you're using Tomcat, you often use it with Apache Web Server. If you're using JBoss, you also need an HTTP server and a servlet engine (Jetty or Apache Web Server and Tomcat).
Dig deeper on SOA, XML and Web Services Development Tools
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations.continue reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well.continue reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.