tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Re: AJP Todo
Date Sun, 02 Dec 2001 01:37:32 GMT
On Sat, 1 Dec 2001, Remy Maucherat wrote:

> Hi,
> On the TODO list for AJP, there is:
> - Implementing jvmroute.

Unfortunately that's not that easy. Manager has no way to access the
Request, and that means no way to get the jvmRoute.

The only possible hack is to 'intercept' the cookie header in jk and
rewrite it in both directions ( to extract and insert the jvmroute ).

Pretty ugly, but I see no other way with the current API.

I'll try to do the hack, but I want to first finish the refactoring.

> - Adding a mechanism like there is in Tomcat 3.3 to automatically generate a
> configuration file. That should be relatively easy to do using a server
> listener (or a host listener).

Hmmm. That shouldn't be difficult, but I would wait with it too.

There are some major simplifications in jk2 configuration, and
I think it is possible to have a much cleaner solution to synchronize
web.xml/server.xml and httpd.conf/

Porting the 3.3 config generator would be great as a temporary solution,
if anyone has the time.

> I'm not going to do either of these. I have no clue how to do the first one,

To be honest, I have no clue either ( except for the hack - which is
what I'll probably do if nobody find a better solution ).

> Tomcat 4. I did bootstrap the porting of the docs already, and I've also
> fixed the problems with compiling against the CVS HEAD, so I think I've done

Great, many thanks !

> my part :) If you want to see full support for AJP in TC 4.0.2, it's up to
> you guys :)

Well, if you can also port the 'trusted app' - it would be really great.

For 3.3 jk will be packaged as a 'trusted web application' ( i.e. a WAR
with an extra interceptors.xml ), so users can deploy it / update it /
etc as simple as with any other application.

For 4.0 we create the jar that will be put in lib/catalina/..., but
it would be nice to be able to use the same .WAR file.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message