It is me ... I wasn't calling the other context rather just a resource
within the context
Peter Johnson wrote:
Ok, I gave this a test run, so from app1 I called
req.getRequestDispatcher("/app2").include(req,res);
However, it seems that doing this loops i.e. re-requests app1 rather
than passing t
Ok, I gave this a test run, so from app1 I called
req.getRequestDispatcher("/app2").include(req,res);
However, it seems that doing this loops i.e. re-requests app1 rather
than passing the request to app2. It this an error with Tomcat or a
misunderstanding by me?
PJ
Peter Johnson wrote:
it would
it would seem to be as simple as
req.getRequestDispatcher().include(req,res);
PJ
Peter Johnson wrote:
Thanks for the quick reply QM ...
I'd be writing both the "parent" and "child" apps. Basically the
parent would act as a broker to the child apps and perform the
"decoration". I guess SiteMesh d
Thanks for the quick reply QM ...
I'd be writing both the "parent" and "child" apps. Basically the parent
would act as a broker to the child apps and perform the "decoration". I
guess SiteMesh does a form of automated "screen scraping". I would do
this so that all "child" apps may have a common
On Wed, Mar 02, 2005 at 11:53:52AM +1100, Peter Johnson wrote:
: I was just wondering if it was possible to pass a request to another
: context within the same host and capture the output. If it is, any
: suggestions on the best way to do so?
You could make a URL call to the app (java.net.URL an
Tomcat 5.5.7
Hi all,
I was just wondering if it was possible to pass a request to another
context within the same host and capture the output. If it is, any
suggestions on the best way to do so?
Basically, I am planning to use SiteMesh for site templating however
would prefer to deploy many of
