RE: Is it possible to bind a web-app inside an EAR to a specific http port or virtualserver?
with regards to Glassfish Listeners:
By default, when the Enterprise Server starts, it has the following HTTP listeners:
Two HTTP listeners named http-listener-1 and http-listener-2, associated with the virtual server named server.
An HTTP listener named admin-listener, associated with the virtual server named __asadmin.
http-listener-1 uses port 8080, http-listener-2 uses port 8181, and admin-listener uses port 48489.
The default virtual server is the server to which the HTTP listener routes all request URLs
whose host component does not match any of the virtual servers that are associated with the HTTP listener (a virtual server is associated with an HTTP listener by listing the HTTP listener in virtual-server attribute).
Each HTTP listener has a default virtual server.
if virtual-server is the way you want to apporach
we will need to have at least one Listener we have one IP:port for each Listener
(or At least one Listener with a default virtual-server)
with virtual-server we would need to add
allowRemoteAddress for the SOAPServer
2)a Redirect property
3)possible custom authRealm defined in web.xml
authRealm..i dont know these params for your particular SOAPServer config
Here is the doc for
"redirect to a Different Host"
If a client sends a Host: header, that host name supersedes the HTTP listener’s server name value in redirects.
Specify a redirect port to use a different port number from that specified in the original request. A redirect occurs in one of these situations:
If a client tries to access a resource that no longer exists at the specified URL (that is, the resource has moved to another location), the server redirects the client to the new location (instead of returning a 404), by returning a designated response code and including the new location in the response’s Location header.
If a client tries to access a resource that is protected (for example, SSL) on the regular HTTP port, the server redirects the request to the SSL-enabled port. In this case, the server returns a new URL in the Location response header, in which the original insecure port has been replaced with the SSL-enabled port. The client then connects to this new URL.
Where the virtual-server redirect "
Last year I did this redirect in code and as long as there are no intervening Servers or proxies blocking redirect Host:Port this will work
Does this answer your question?