> -----Original Message----- > From: Mladen Turk [mailto:[EMAIL PROTECTED] > Sent: Monday, July 19, 2004 5:58 AM > To: 'Tomcat Developers List' > Subject: RE: Some JK2 ideas v.3 > > > > > -----Original Message----- > > From: Henri Gomez > > > > We should first determine if Apache2 will have to monitor a > > service/system links to the various tomcats (in cluster > > configuration) to learn about real-time topology. > > > > In fact, that is why I've pursued the .xml config over the current one. > The main idea is to _internally_ have config tree (right now we don't have > that). > So that internal configuration tree will be populated either using > directives in the native httpd.conf or reading server.xml stream from TC or > from file. > > > > > > > - the configuration should be in Apache's config file, rather than > > > some complex properties file > > > > +1 > > > > The general idea is to connect to TC and get the URI/VHOST topology, but we > still need the 'intervene' directives for connector specific ones. > How to make them simpler to use the JK and JK2? >
This is a good idea if we allow a way to exclude tomcat URI's from being available to apache. Right now I can exclude a URI from apache(no JkUriSet), but still use it when connecting to tomcat on another port - i.e. /manager. > Perhaps using something like: > > <CoyoteWorker workerA> > ...directives > > </CoyoteWorker> > I also like this idea. May I suggest <TomcatWorker workerA> as a more intuitive name for the Apache admins not familiar with the name of tomcat's connector? Charlie
