Re: How to get around a tricky situation.

Hello You could also create a new "empty" context called /images with docbase properly set to the location of your images. This context will serve your images. Jacob Kjome a crit : the loading of images is a function of your browser after the page has been sent by the server to it. The

Re: How to get around a tricky situation.

On Tuesday 03 April 2001 09:23, Alex Colic wrote: Hi, I need some advice on how I might fix a problem with one of our web apps. We farmed out an app that works ok except that the web pages which are created by servlets are looking for images in the tomcat root images directory. This

Re: How to get around a tricky situation.

Just so I understand, to do the below I would have to modify my server.xml file...correct? This cannot be done in my web.xml file? Thanks Alex Date: Wed, 04 Apr 2001 09:47:56 +0200 To: [EMAIL PROTECTED] From: =?iso-8859-1?Q?St=E9phane?= BAUDET [EMAIL PROTECTED] Subject: Re: How to get around

Re: How to get around a tricky situation.

web.xml file? Thanks Alex Date: Wed, 04 Apr 2001 09:47:56 +0200 To: [EMAIL PROTECTED] From: =?iso-8859-1?Q?St=E9phane?= BAUDET [EMAIL PROTECTED] Subject: Re: How to get around a tricky situation. Message-ID: [EMAIL PROTECTED] Hello You could also create a new "empty&quo

How to get around a tricky situation.

Hi, I need some advice on how I might fix a problem with one of our web apps. We farmed out an app that works ok except that the web pages which are created by servlets are looking for images in the tomcat root images directory. This presents a problem in that if I create a war of our app I also

RE: How to get around a tricky situation.

the loading of images is a function of your browser after the page has been sent by the server to it. The only way I can think of doing this (barring some funky Java class like ReturnImagesFromContextInterceptor.class, which I'm not sure how you'd do?) is to prefix all your /images/