Hi,
A couple of suggestions.
>Basically, we develop all of our applications under contexts. Each one
a
>separate context. When they go live, they go to the default context so
>users
>don't have to request everything with "/context/blah". This means that
if
Don't do this. Deploy them to their own contexts if possible. This
will let you do much more later in terms of security, administration,
etc. If you're really hung up on users not having /context in their
bookmarks, have some redirect files (just for the app entry points: the
things users would bookmark) in the root context.
>the application has links to "/<context>/anything.jsp" or
>"/<context>/servletpath" (instead of "anything.jsp" and "servletpath")
>they'll break. So I guess my real question is, what's the best way to
>design
>the application so these problems don't arise. Or is this just a
>configuration issue?
Use relative links. For example, if this is your structure:
/myApp
-- some html files here
-- /jsp
-- /images
-- /WEB-INF
-- web.xml
-- lib
-- classes
For a JSP to link to an HTML page, it would use
<a href="../someHtmlFile.html">File</a>
For a servlet to link to a JSP:
<a href="../jsp/jspFileName.jsp">JSP</a>
etc.
Keep all links relative. No /myApp/jsp/someJsp, just ../jsp/someJsp.
It'll save you trouble ;)
Yoav Shapira
Millennium ChemInformatics
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
