My 2 cents:
1) I always try to serve my images from another server (Apache Web Server) configured to serve all the static content, and only send requests to my app server that actually require the app server. As a side effect, paths are easier to manage as they don't change when your application context path changes.
2) If I do serve images from my app server, I definitely don't want my controller servlet processing those requests, as there is no need for logic.
Erik
Scott Purcell wrote:
Hello, As I am building a new (frist time) struts app. I am looking for some insight as to the best way to handle jsp page images.
To make a long story short, my folder structure is this: /dealer /dealer/images /dealer/WEB-INF /dealer/etc.
So all my <img src="/images/etc."> were like this. But because of some IPlanet configuration, my admin, told me we have to change our folder structure so not it is like this: /dealer/webapp /dealer/webapp/images /dealer/webapp/WEB-INF /dealer/webapp/etc.
But for some reason the dns is looking at /dealer/webapp as one entity. And I would have to put the /dealer/images in front of all paths. This is ok, but when I use the html:img tags, some tags seem to use the context and I can use /images again. But others do not.
I figured this group has probably built quite a few struts apps, and I am looking for some "best practice" ideas, because this app will be deployed many times and I do not want to change links later on in the pages.
Thanks, Scott
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
