Javax.xml.ws.Endpoint.publish(String address), the address should be escape

Question

Hi,
javax.xml.ws.Endpoint.publish(String address), the address should be escaped or not?
For example,
Endpoint.publish("http://localhost:9090/test test", new TestImpl());
or
Endpoint.publish("http://localhost:9090/test+test", new TestImpl());
or
Endpoint.publish("http://localhost:9090/test%20test", new TestImpl());
And in the WSDL, the service location should be
<soap:address location="http://localhost:9090/test test" />
or
<soap:address location="http://localhost:9090/test+test" />
or
<soap:address location="http://localhost:9090/test%20test" />
Any comment will be appreciated!
-tong

Answer 1

I spent some more time on this subject, and basically, if one steps out of the ordinary WebServices stuff (that is, using web.xml for declaring services, and deploying on a standard servlet container server like tomcat or websphere), then things are a bit more complicated. In the ordinary case with tomcat and others, it is the server that will take on an HTTP request, then instantiate the servlet, contain it in a container, and have the request handled. If you on the other hand want to define your servlets beforehand, and be ready to handle HTTP requests, the whole point is that one needs to find a servlet transport mechanism that can host the WebService. And there are not many options, with in fact the only one being referenced is the Apache CXF Servlet that is Spring disabled. It looks more as a dirty hack than anything else, but one does not have any other option, as there is no real servlet container implementation in javax(.servlet). Well, there is, e.g. the HttpServlet, but if you opt for that, then you need to do write your own SOAP handler to deal with WebServices.
I will give it a try to have the Helios Thing Handlers bind the OSGi HttpService, and have them register themselves as Servlets on the already present Jetty. I am curious how this work in term of life-time management, e.g. HttpService being available, or not and so forth.
In any case, the standard javax.ws API is working well, e.g. it creates a light and standard Sun provided http server, which is maybe not ideal, but it works wonderfully well.
Maybe one day we will provide not only a full REST interface to OH, but maybe also a full SOAP WebService interface so that OH can be interconnected with other services or parties.