Thanks. Completely agreed with the arguments for not having the API. Right now we put the port numbers in our own projects property file also, apart from server.xml. May be thats the way to do it.
-Saugata --- Rick Knowles <[EMAIL PROTECTED]> wrote: > Having this as a requirement makes an awful lot of > assumptions about the > architecture of the container, none of which are > helpful in the larger > scale. For example, what if you have 2 (or 50) http > connectors and the > same for https ? And then what about ajp13 ? Or > mod_caucho's protocol (I > think it's called hessian) ? The reason this is not > in the servlet api > spec is because it would create more problems than > it would solve. > > There are some cases where you just need to know > what your deployment > environment is going to be ... this is one of them. > > Rick > > saugata ghosh wrote: > > >request.getServerPort() > >-Thanks, but this returns the port number of the > >current request port. > >But my problem is, say the request is for http: and > I > >want to redirect to https:/.../somefile.jsp. - then > ? > >Basically what is required is a method that will > >return the port number set in the conf/server.xml > >file. > > > >-Saugata > > > > > -- > Servlet v2.4 container in a single 140KB jar file ? > Try Winstone > (http://winstone.sourceforge.net) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________ Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! http://advision.webevents.yahoo.com/yahoo/votelifeengine/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
