The server side part (this where you provide some WS endpoint to the world) depends on an endpoint deployment model and transport layer. For EJB3 endpoints we currently use the jboss ejb3-deployer and generate a webapp that is deployed to tomcat. Transport is therefore provided by tomcat.

There is standard WS endpoint deployment API in the pipeline which is not yet part of JSR224. If standalone endpoints are needed, I would like to support that API. Remoting is also not yet ready for server side HTTP trasport AFAIK.

Tom Elrod wrote:

I have both a raw http(s) transport which is basically a standalone web server as well as a servlet transport which runs as a web app within a web container. Will also be releasing a APR transport based off of the APR connector (the stuff Mladen did for JBossWeb).