I figured it out. It turns out the module configuration is getting overwritten by the configuration of another module. Answers to your questions inline.
> But what is getting close to off-topic, is being confusing in your > explanations, to the point of making people wonder what exactly you are > trying to achieve. This can be easily explained. I am a C programmer trying to sink my teeth into Java and webapps and still learning to think in those terms and terminology :) I am trying to set up mod_proxy_ajp to bridge apache and tomcat. I did succeed in being able to call jsps and servlets directly in the webapp but am running into problems when the servlet sends back a jsp file. The client will always see the webapp code as residing under /test/ and so any response to the client will need to have the hrefs pointing to /test. But by using the RequestDispatcher the resource is getting created as /A/ > What exactly is the layout below your Tomcat /webapps/ directory ? The webapp is in /webapps/A/ in my tomcat directory. # ls /webapps/A/ # index.jsp jsp META-INF WEB-INF # ls /webapps/A/jsp/ # hi.jsp > Why do you insist on redirecting your calls to that "/webapps/A/" place when > obviously your servlets or jsp pages live under "/webapps/jsp/" ? > Why do you think you need a RequestDispatcher ? Isn't this the way to send a new resource to the client in response to a invoked servlet? I probably still have a lot to learn but this I thought is standard. More so when I talk directly to tomcat over 8080 the RequestDispatcher code works. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
