How to support variable context path?

Question

I need to write a webapp, using Jetty. My context path is decided externally and will vary from one customer to the next.

Is this a normal requirment?

Assuming I have links to other pages, AJAX calls from static JavaScript files and image references from static CSS files, how can this be achieved? What is the recommended project structure?

Can I accomplish this without templates? (JSP).

So you're saying you'll be deploying the same webapp multiple times in the same container, under different names? — Tap, Jun 03 '13 at 16:35
Looking for [this](http://stackoverflow.com/a/57595/354831) ? — Alexandre Lavoie, Jun 03 '13 at 17:33
Use the `` tag? What do you mean, "without templates"? How do you create the view? — Dave Newton, Jun 03 '13 at 18:20
Here is the example of how to add external references in JSP **without hard-coding context path**: [Adding external CSS in JSP](http://stackoverflow.com/a/14571407/814702) — informatik01, Jun 03 '13 at 21:07

score 1 · Answer 1 · answered Jun 03 '13 at 18:22

Is this a normal requirment?

Yes. Nothing in your webapp should depend on the value of the context path.

It's actually quite simple to support any context path: systematically prepend the context path to every URL your app produces.

In JSP files, use the <c:url> tag (or similar) to generate URLs.

In JS files, use URLs passed from the JSP pages, or use a global variable set in theJSP file and containing the context path to generate the URLs.

In Java files, use request.getContextPath() to get the context path and prepend it to URLs.

In CSS files, use relative paths.

How to support variable context path?

1 Answers1