Hey all, I just decided to package my webapp as a WAR and deploy it into a local Tomcat install. Up until this point, I've been accessing the app using JettyLauncher and things have been working great. So, I was a bit surprised to see all of my image paths were messed up when I deployed the WAR.
It turns out the problem that I made all of my paths relative to /. So, all of my image paths are /images/something. This was to avoid using relative paths like ../../../images/something. Turns out while using JettyLauncher, I always deployed to the root context, so no issues. Deploying the WAR however has left me with something like http://localhost:8080/webapp/. So, all of my links point to an invalid location. I realize I can configure the webapp to be in the root context of Tomcat, and I may just go that route. Is there a better way to do this though? I'm thinking using assets might help, but I'm looking to keep things as clean as possible too, so if I can cut out complexity, all the better. Sorry for such a basic question. I've probably run into this once before, but I really don't recall how I dealt with it. Thanks, Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
