Now that we have sslservlet in addition to servlet, I'm trying to figure out the easiest way to configure my web container to support both.
Here's the use case - I have a remote client that, depending on how the customer wants to configure it - can talk unencrypted/unsecured back to the server or can talk securely via SSL. I don't want the customer to have to configure alot of things - it would be nice for the server to support both servlet and sslservlet transport and just have the remote client determine how he wants to talk back to the server.
Looking at the readme.txt in src/tests/org/jboss/test/remoting/transport/servlet/readme.txt, I see the web.xml files the tests use have basically the same servlet definition - the only difference is the locatorUrl param. What if I continue to use the older "locatorName" param and not specify locatorUrl?
This means the servlet won't know what transport it used (could be servlet or sslservlet). But I don't think it matters. So long as the request makes its way to the servlet, it will process it the same way. So, whether the request went through the SSL connector over port 8443 or over the standard port of 8080 (unsecured), it doesn't matter - the request will be processed the same.
As long as my server has both 8080 and 8443 configured properly, this should work. Is that a correct assumption?
Right. If you use the sslservlet on the server side and the server.xml for tomcat has both 8080 and 8443, then client can select which it wants to connect to. I am pretty sure you can even use the sslservlet on the client without setting the ssl properties and will work fine connecting to the sslservlet on the sever, just need to use port 8080.