* Turner, John <[EMAIL PROTECTED]> [1201 14:01]: > > Not sure what JK2 needs to work, I don't use it. You should be able to > build it from the same source package as JK. I was able to do so on my Red > Hat test box, but it took quite a bit of hacking around.
But you need a local install of Java; is that right? > JK isn't really "deprecated", the dev team is just pursuing JK2. In my > opinion, JK is quite stable and JK2 is not ready for "prime time", though > that is my personal preference. Ok, thanks. I setup a Coyote/JK2 Connector on the tomcat side and used mod_jk to forward AJP13 requests to it. That seems to work pretty well, although am I right in thinking a JkMount command can only forward URIs 'as-is'? i.e if I set JkMount /neotokyo/* lb then the request is going to be sent as a request to /neotokyo/whatever.jsp - that is, as a request for whatever.jsp in the context neotokyo to the default Host element in my engine? I might have missed something, but don't see how else it could work. The workers aren't URL aware, they just shovel requests into sockets. Doesn't this mean that if you mapped *.jsp, you'd need either a ROOT context with directories mirroring Apaches tree, or a Context for each top-level directory on the Apache side? And is the Host part of the protocol, so you can dedicate virtual hosts to AJP clients? I got around this by having a Tomcat virtual host with the DNS name of the Apache webserver, and setting it as the Engines default host - since no HTTP requests should come into tomcat asking for that host, it solves the problem but is pretty clanky. If these seem to be odd questions, bear in mind I'm comparing this to a mod_proxy / Coyote Proxy Connector solution, which seems more flexible on first impression. I just wanted to be sure I know how this works, also does anyone know if jk2 addresses these issues? Thanks a lot. -- Rasputin :: Jack of All Trades - Master of Nuns -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
