You're right, include and forward will
always resolve to the current application context.
All is not lost, since there are ways to communicate between contexts. The problem is that it is highly vendor specific and if you really want to do this you're going to have problems.
It goes like this:
A RequestDispatcher can load (ie include of forward to) a JSP, but a RequestDispatcher is specific to a ServletContext.
From a
Servlet, you can get the ServletContext, from a ServletContext you can get a handle to another (named) ServletContext.
From this ServletContext, you can a RequestDispatcher to load the resource.
That's it in theory, as to how it actually works in the server you are using, who knows.
I'd still recommend a sendRedirect to the resource in that context.
(Problems you'll possibly run into: the named context may or may not require a leading slash, since the RequestDispatcher may exist on the other sde of the
Thread pool its possible the include could happen just about anywhere in the output. Good luck
)
Dave