Craig, I knew I should have put that tidbit in my email - it was in my first revision. I took it out because it sounded too preachy in my first draft. I agree with you since the product I'm working on has every virtualhost mapped to one Tomcat context for application sharing.
As we've read, Martin seems to be assuming the opposite (exactly one context for his customer) and has his mind 100% stuck on MAGIC setup the very first time. Personally, I do not see anything wrong with waiting for the first SOAP or HTTP call to perform the setup steps. Even if that first call takes 20-30 seconds (read: outch!), further calls will be instant. If you save that URL somewhere (file, DB, etc.), the plugIn can "know" that information and upon further webapp restarts perform initialization instantly so no further wait occurs. If Martin is 100% sure of his future clients' setup(s), my suggestion could work. Heck, he could even make those conditions a requirement for deployment: port 80 and a specific context on both the web server and java app server. That doesn't seem like much of an issue for "selling" something. Regards, David -----Original Message----- From: Craig McClanahan [mailto:[EMAIL PROTECTED] Sent: Thursday, January 27, 2005 1:06 AM To: Struts Users Mailing List Subject: Re: PlugIn and the base URL On Wed, 26 Jan 2005 13:32:50 -0500, David G. Friedman <[EMAIL PROTECTED]> wrote: > A Devil's Advocate says: > > I agree with the theory that the webapp Context name within the application > server "/myapp" should be available to the servlet but not the > host/port/etc. The assumption that a particular webapp only has one context path -- or even one host:port combination -- is not in conformance with reality on most modern servers. Consider, for example, how many environments are set up such that "www.mycompany.com" and "company.com" resolve to the same webapp. The same sort of aliasing of the context path is trivially simple in any modern web server or app server. Application architectures based on the assumption that there is one-and-only-one URL for the app should be rethought. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]