> The cause for some of these specs is the fact servlet containers aren't required to run on file systems. For example, they may run entirely inside a DBMS (and Oracle had such a container for a while), in which case you must deploy in a packed WAR and the subset under a server's URL name space is not a hard-drive path.
Nobody "cares" if this maps to a file system or not. If your application needs to create an URL that will take someone to a page on your site (let's say it's the /login.jsp page), we need to be able to set the protocol, domain, port and context path that will appear in front. For example, we have lots of emails that go out with such links back to the webapp, and today, we end up putting the complete URL in config files since there's no easy way to set these up in an "init" type method. That's just too bad since the context path doesn't change from request to request. David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
