Hi, The spirit of the servlet specification calls for every webapp to be self-contained and portable. Using DefaultContext by definition means your webapp depends on server-global settings. It's a subtle but significant difference from it depending just on its own server configuration (in this case its own Context element or its equivalent in other servers). This is not the end of the world as far as portability or self-containment goes, and if this is your worst design mistake then you're in great shape, but nonetheless try not to overuse it.
And of course your point about having many hosts mitigates your choice. Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: wsedio [mailto:[EMAIL PROTECTED] >Sent: Friday, May 21, 2004 5:58 AM >To: Tomcat Users List >Subject: Re: equivalent of DefaultContext element for Host > >On 20-05-2004 16:03, Shapira, Yoav wrote: > >> Be careful when relying on the DefaultContext, it can lead to laziness. > >Can you be a bit more specific? :-) > >I am dealing with a bunch of virtual hosts ... > >Thanks. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
