You do not want to hard-code all the images in your application. What happens if your company starts selling a new part, or if an image of an existing parts needs to be updated? You don't want to modify, build and re-deploy your EAR file everytime that happens.
You can put them anywhere in the file system and make a
servlet that can serve the images (the servlet would read them from the directory where you put them), or you could even put the images in a database and make a servlet that retrieves them from there. I guess you already have a database that contains all the information about the parts you're selling?
[ October 13, 2005: Message edited by: Jesper de Jong ]