Best Practice: separating images from main application WAR

[Brice Ruth <br...@fiskars.com>]

Greetings.

In the now-live "fiskars.com" site we have oodles of product images 
(somewhere in the neighborhood of about 5000). Now, currently, all our 
images are tracked through CVS, which is a good thing. Also, they are 
all packaged in the the deployment WAR (/products/.../). Now, ideally, 
I'd like to split out the images into their own WAR or something to that 
effect ... while still being able to use the Struts-Html <html:img 
page="/.../"> tags, or something similar to it. Thankfully, references 
to the product images are limited to only two content tiles (one shows 
thumbnails, the other shows the full image and has a pop-up link for a 
zoomed image). I'm just not sure what the best way is of segregating 
things out. I have a second web application (internal) that also needs 
access to these images, ideally, images used by the public fiskars.com 
web application will always be in-sync with the internal 'management' 
web application. Currently, that's not the case as these ~5000 images 
are checked into two separate CVS modules.

So, am I looking at creating a third "product images only" CVS module 
and then doing something with that, or what would you recommend? Any 
previous experiences, tips, pointers, whatever - always appreciated.

TIA!

-- 
Brice D. Ruth
Sr. IT Analyst
Fiskars Brands, Inc.


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org