d) Integration with http-provider. http-provider is being re-worked in 4.7: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=157057&a... I respect Kev's comment: &quot;Kevin.Conner(a)jboss.com&quot; wrote : can we please get the http gateway working first before we go off track and implement other features? , however I just want to make sure we don't implement anything that would preclude the following two enhancements, based on a URL that looks something like: http://host/context/http/${service.category}/${service.name} 1. Possibly introduce a new property on SOAPProxy, like: <property name="publish" value="true"/> , similar to EBWS's ability to auto-publish an endpoint. This way you don't have to define an http-provider or http-listener. The default for this would be false, but if true, it would go with some sensible defaults. 2. Make sure that wsdl is available via the http-provider for published SOAPProxy endpoints via the "?wsdl" suffix convention: http://host/context/http/${service.category}/${service.name}?wsdl This could be implemented via a simple servlet/filter that just request-dispatches to the wsdl already exposed via the contract app. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245398#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...