I didn't have any luck at all with this. I'm going to give up and make the Tomcat side match what I want on the Apache side. It's far less convienient for me, but so be it. I propose a new feature that takes care of this issue, maybe called "uriAlias"?
Opinions?
--Aaron
Chris Dodunski wrote:
Well, I redefined DocumentRoot and <Directory> in [Apache Home]/conf/httpd.conf so I could navigate to [Tomcat Home]/webapps (via JK2), but perhaps this isn't the way it's best done - although it works. Previously I could only navigate to [Apache Home]/htdocs. I would like to hear more on this also.
Chris.
-----Original Message----- From: Aaron Paetznick [mailto:[EMAIL PROTECTED] Sent: Wednesday, 19 March 2003 9:53 a.m. To: Tomcat Users List Subject: Re: Arbitrary Tomcat mounting in Apache
The actual location of the cocoon directory is _outside_ any DocumentRoot or Directory definition. Is that my problem? I would not have suspected that at all because, and please excuse my ignorance, I thought mod_jk2 was more or less a glorified mod_proxy tailored for ajp13.
I'll try tweaking my Directory and DocumentRoot definitions and let the list know how it goes.
--Aaron
Chris Dodunski wrote:
Hi,
What is 'DocumentRoot' and the <Directory> tag set to in [Apache Home]/conf/httpd.conf? Where is 'cocoon' in relation to this?
Chris.
-----Original Message----- From: Aaron Paetznick [mailto:[EMAIL PROTECTED] Sent: Wednesday, 19 March 2003 5:45 a.m. To: [EMAIL PROTECTED] Subject: Arbitrary Tomcat mounting in Apache
I apologize because I've sent this email already with the subject "JK2 context mounting", but I didn't get a response.
I want to be able to mount a Tomcat URI at any arbitrary location in Apache. Apache and Tomcat are currently working with the mod_jk2 connector with existing Tomcat URIs. I'm using Apache v2.0.44, Tomcat v4.1.18, and mod_jk2 v2.0.3-dev on Solaris 9.
Here is some of my workers2.properties file:
[uri:/cocoon/*] context=/cocoon/
[uri:/someapp/*] context=/cocoon/someapp/
..when I use just the first (/cocoon/) entry, /cocoon/someapp/ works fine. When I add the second (/someapp/) entry, both locations spit out a 404 error. I can't seem to find any other possible configuration method to do this with. This has to be a common problem and question.
I've searched Apache.org and Google extensively for the answer, but it's no good. I even considered trying mod_webapp, but I'm using the worker MPM (i.e. threaded) which mod_webapp doesn't like. The "uriMap" config sounds promising, but there is zero documentation for it, and I couldn't get it to do anything useful while I was experimenting.
Can anybody help me out? Thanks!
--Aaron
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
