Well, it is almost useless to do this anyway because Apache Web Server would have to be restarted to pick up the modified JkMount stuff...unless you put that info inside an .htaccess file. What I tend to do is, in advance, figure out all the applications I plan to run in the near future and add the following JkMounts....
JkMount /mypossiblyexistingcontext ajp13 JkMount /mypossiblyexistingcontext/* ajp13 That way, my Apache Web Server is always ready for apps that I install via the Tomcat manager app. Jake At 09:47 PM 8/12/2002 -0700, you wrote: >Hi, > I have tomcat 4.03 and apache 1.3, installed and >running fine. My issue, is when I deploy a web >application using tomcat's manager service, then the >conf/auto/mod_jk.conf is not regenerated. > >How do I configure tomcat to regenerate the >mod_jk.conf file when the manager service deploys a >new web application? > >Thanks > > >__________________________________________________ >Do You Yahoo!? >HotJobs - Search Thousands of New Jobs >http://www.hotjobs.com > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
