Sorry, I looked back in the thread, but I'm not clear what the problem is.
The example mod_jk.conf file clearly has a virtual host for each Host, and a Directory and Alias container for each Context. This is demonstrated by the fact that /manager and /admin are dynamic Contexts, but have a Directory and Alias.
What is it that you need that isn't happening? Every "Host" element in server.xml is a "virtual host", so whether you want to "avoid this virtualhosting feature" or not you will have to put a Listener element within your Host element. You have to have at least one Host element in server.xml.
My HOWTO describes exactly where to put the Listener elements to generate the mod_jk.conf example file I posted, which does have the three Jk* directives.
http://www.johnturner.com/howto
John
On 20 Mar 2003 17:09:31 +0100, Vincent Panel <[EMAIL PROTECTED]> wrote:
OK, thanks. It still seems impossible to avoid this "virtualhosting" feature if you do not want it.
Moreover, after setting exacly the same parameters than (both of) you, these three lines do not appear in my mod_jk.conf :
JkWorkersFile "/usr/local/jakarta-tomcat-4.0.4/conf/jk/workers.properties" JkLogFile "/usr/local/jakarta-tomcat-4.0.4/logs/mod_jk.log" JkLogLevel emerg
But that's OK, I'll wait for another version adding a bit more flexibility. Meanwhile, I'll play it manually.
Thank you all.
Vincent.
On Thu, 2003-03-20 at 16:12, John Turner wrote:
Here's an example of exactly what it creates:
http://www.johnturner.com/howto/mod_jk_conf.html
John
On 20 Mar 2003 16:06:41 +0100, Vincent Panel <[EMAIL PROTECTED]> wrote:
> OK, thanks
>
> But it generates <Virutalhost> directives and inside, there's only
> JkMount's, no <Directory>, no Alias, right ?
>
> What I really need (and I'm pretty sure I'm not the only one) is
> something like this (for each of my contexts) :
>
>> >#
>> ># The following line makes apache aware of the location of the >> /examples
>> >context
>> >#
>> >Alias /examples /var/tomcat4/webapps/examples
>> ><Directory "/var/tomcat4/webapps/examples">
>> > Options Indexes FollowSymLinks
>> ></Directory>
>> >JkMount /examples/servlet/* ajp13
>> >JkMount /examples/*.jsp ajp13
>> ><Location "/examples/WEB-INF/">
>> > AllowOverride None
>> > deny from all
>> ></Location>
>
>
>
>
> On Thu, 2003-03-20 at 15:56, Jacob Kjome wrote:
>>
>> Close. One inside the <Server> tag and one inside each <Host> tag that >> you want autogenerated.
>>
>> Here's mine...
>>
>> <Server ....>
>> <Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
>> modJk="mod_jk.dll"
>> jkDebug="info" />
>> ...
>> ...
>> ...
>> <Host ...>
>> <Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
>> append="true"
>> forwardAll="false" />
>> ...
>> ...
>> ...
>> </Host>
>> ...
>> ...
>> ...
>> </Server>
>>
>> Jake
>>
>> At 02:09 PM 3/20/2003 +0100, you wrote:
>> >Well, thanks, but I've already read this. It is not really explaining
>> >WHERE are supposed to be those "Listeners" that turn tomcat >> ApacheConfig
>> >on.
>> >
>> >When you read the doc, it seems that you're supposed to put one >> listener
>> >inside the <Server> tag and another one inside each <Context> tag
>> >(remember I do not want to use Virtualhosting). It's not clear whether
>> >you're supposed to use append="true" or not. In any cases, it does not
>> >generate what I want (and there also seems to be some bugs in here :
>> >restarting tomcat twice does not give the same mod_jk.conf). I've also
>> >tried to put them in many places whithout success.
>> >
>> >However, I recently found a mod_jk.conf shipped with a RedHat RPM and >> it
>> >seems to have been auto-generated as it contains the following lines :
>> >
>> >#
>> ># The following line makes apache aware of the location of the >> /examples
>> >context
>> >#
>> >Alias /examples /var/tomcat4/webapps/examples
>> ><Directory "/var/tomcat4/webapps/examples">
>> > Options Indexes FollowSymLinks
>> ></Directory>
>> >JkMount /examples/servlet/* ajp13
>> >JkMount /examples/*.jsp ajp13
>> ><Location "/examples/WEB-INF/">
>> > AllowOverride None
>> > deny from all
>> ></Location>
>> >
>> >
>> >This group of directives is exactly what I need but I don't know how to
>> >tell tomcat to generate them automatically. I'm almost forced to make >> a
>> >perl script to do something like "For each context you're managing,
>> >generate an Alias, a Directory and a JkMount for Apache" (using perl to
>> >manage a java application server... a bit strange isn't it ? :-)
>> >
>> >
>> >On Thu, 2003-03-20 at 10:04, Bill Barker wrote:
>> > > If it wasn't deprecated, I'd probably go back and add a 3.3-style >> all-in
>> > > directive to the 4.x auto-config.
>> > >
>> > > In the mean-time go back and read
>> > > > http://jakarta.apache.org/tomcat/tomcat-4.1->> doc/config/jk.html#Using%20Apach
>> > > eConfig.
>> > >
>> > > "Vincent Panel" <[EMAIL PROTECTED]> wrote in message
>> > > news:[EMAIL PROTECTED]
>> > >
>> > >
>> > >
>> > >
>> > > ------------------------------------------------------------------
--- >>
>>
>> > > To unsubscribe, e-mail: tomcat-user- [EMAIL PROTECTED]
>> > > For additional commands, e-mail: tomcat-user- [EMAIL PROTECTED]
>> > >
>> >
>> >
>> >
>
>
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
