On Sat, 1 Dec 2001, Bill Barker wrote:
> I have no objection to help porting ${Server}Config to 4.x, but I'm still a
> Catalina novice. The 3.3 API is more command and control, so it is easier
> to get to the information. It will take me a little time to find out how to
> get the servlet-mappings in Catalina.
I'm a bit unhappy with the config generator in 3.3 - I think we can do
better.
If you want to work on this, it would be great to make it a bit more
independent of the container. Right now it is very tightly coupled,
in order for it to work you need to start tomcat, it doesn't work very
well with context reloads, etc.
Of course, we don't have any way to change the mappings without restarting
apache, but that can be fixed as we add more ajp14 features ( jk_uriMap
can be changed at run time, we just need the protocol support to send
update requests ).
One idea was to generate a .properties file for each webapp, following the
same style with webapps/ directory. If a webapp is reloaded we can
regenerate the app's mappings and get jk to reload only that file.
We could also use a bit of XSLT or a xmlmapper to do that from web.xml,
without starting the server. This would allow the configuration to be done
'off line'.
Costin
> ----- Original Message -----
> From: "Remy Maucherat" <[EMAIL PROTECTED]>
> To: "Tomcat Developers List" <[EMAIL PROTECTED]>
> Sent: Saturday, December 01, 2001 4:40 PM
> Subject: AJP Todo
>
>
> > Hi,
> >
> > On the TODO list for AJP, there is:
> > - Implementing jvmroute.
> > - 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).
> >
> > I'm not going to do either of these. I have no clue how to do the first
> one,
> > and no time to do the second one.
> > So I'm counting on all the guys who voted +1 for supporting AJP 1.3+ on
> > 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
> > my part :) If you want to see full support for AJP in TC 4.0.2, it's up to
> > you guys :)
> >
> > If people are willing to actively support it, and if the risk for creating
> a
> > security vulnerability is low, we could also enable the AJP 1.3 connector
> > and the server listener by default (and declare it officially supported),
> so
> > that 4.0.2 behaves almost like 3.3 for AJP 1.3 related stuff.
> >
> > Thanks,
> > Remy
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> >
>
>
> *----*
>
> This message is intended only for the use of the person(s) listed above
> as the intended recipient(s), and may contain information that is
> PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
> you may not read, copy, or distribute this message or any attachment.
> If you received this communication in error, please notify us immediately
> by e-mail and then delete all copies of this message and any attachments.
>
>
> In addition you should be aware that ordinary (unencrypted) e-mail sent
> through the Internet is not secure. Do not send confidential or sensitive
> information, such as social security numbers, account numbers, personal
> identification numbers and passwords, to us via ordinary (unencrypted)
> e-mail.
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
