I guess it depends if you are trying to restrict access to these images.
To make all images available for anyone, put them into /images, for example.
If you want to not allow any direct access to them, you could create a
directory under /WEB-INF and put them there. You would then have to
create something to serve the images up to browser.
Or set up container managed security, put them into /auth/images, then
put a security constraint on /auth/images so that only users with the
required role is allowed to view the images.
Murray Collingwood wrote:
Hi all (Gosh, I'm starting to feel like a regular on this list...)
After my experiences below I have rewritten my application to store the images in a
local sub-directory, however when I ran this new version the sub-directory was created
under the Tomcat/bin directory - not really appropriate.
Should I be trying to reference my application directory and store the images under my
"/WEB-INF" directory?
Do I have to setup a special directory on the server that can be referenced by Tomcat
to serve the images directly?
What are others doing?
Also, if you are referencing this directory in your application, is it hard-coded or do you
have an entry in your 'context.xml'? What sort of entry do you use?
Kind regards
mc
--
Jason Lea
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
