There are two parts to a connector. There is the Tomcat part, and the Apache module (or IIS DLL) part. One part is Java code, one part is C/C++.
ApacheConfig is a Java class. Since using it requires you to type in something along the lines of "org.apache.ajp.tomcat4.config.ApacheConfig", that's where you would find the source. It has nothing to do with mod_jk, other than it writes out a text file compatible with mod_jk, which is an Apache module and written in C. On the Tomcat side, there are two main connector classes: Ajp13Connector, and CoyoteConnector. Ajp13Connector is the older method of allowing Tomcat to "speak" JK (aka AJP13). That's all Ajp13Connector does. CoyoteConnector is the currently developed connector class, and is considered stable on the Java side. It "speaks" JK, JK2, HTTP, and HTTPS depending on how it is initialized, and what port it's listening on. CoyoteConnector is enabled by default in 4.1.12+ on port 8009 in server.xml, which is the default JK port. STATUS Webapp: considered usable. Has many major deficiencies, all of which have been discussed many many times. No longer actively developed, no longer actively maintained. No bug fixes. Going forward, use at your own risk. JK: considered usable and production quality. Actively maintained, as far as I know. Many people using it in production, many people familiar with how it works. Apache module considered stable and production ready. Tomcat class considered stable and production ready. Going forward, no new features. Development efforts focused on JK2 (aka AJP14). JK2: considered usable. Considered stable on Tomcat side. Considered "beta" on Apache side, though exact definition of "beta" fluctuates depending on who you ask (JK2 developer, user, whatever). Probably OK for production on Apache side, but could have problems, major or minor. Probably not as many people using it in production as JK. Actively maintained, actively developed. Going forward, the main focus of the connector dev team. Really, I don't mean to get cranky, but all of the above I learned by reading this list for a week or two. I'm not on any of the dev teams, these types of discussions come up daily, or nearly so. As far as the quality of the documentation, there's nothing more to say. If you want it to be better, either pitch in and help or choose a commercial product that has the nice documentation you want to see. Volunteers will be welcomed with open arms and greatly appreciated. Any other discussions are a waste of time. It's really that simple. Comparing one open source project's documentation to another's is comparing apples to oranges....Apache HTTP is a huge, very mature project with a substantially larger development team and a substantially larger installed base. Tomcat is not the same as the connectors. The Tomcat team is under no direct obligation to make web server connectors or actively support/develop same. The Tomcat team only has to support the spec, and the spec doesn't say anything about WARP, JK, or JK2. Using Tomcat with a web server and a web server connector is strictly optional. When you consider that, it's unreasonable to expect ANYONE on the Tomcat team to devote any effort whatsoever to the connectors (aside from HTTP and HTTPS), and it's also unreasonable to generalize and say "Tomcat documentation sucks" just because the connector documentation needs help. HTH John -----Original Message----- From: Joseph Shraibman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 10:33 PM To: Tomcat Users List Subject: Tomcat Documentation WAS: jsps and servlets don't work Jerry Ford wrote: > > With all due respect and recognition to the enormous efforts you > personally appear to have put into making Tomcat accessible, the > documentation is neither comprehensive nor adequate, for either Tomcat > or whatever is the connector du jour. There are pockets of good > documentation, such as your how-tos and seemingly tireless presence on > this mail list, surrounded by lots of chaffe---incomplete, inaccurate, > out-of-date, even non-existent files inside of tarballs or littered > around the jakarta.apache.org website. > I have to agree. Someone on this mailing list said that jk2 is beta. You say jk is deprecated. All I know is I got mod_jk to work, but couldn't get jk2 to work because the documentation was so bad. I didn't even know what the JkMount directive took, so I couldn't figure out that ajp13 needed to be replaced with the name of my worker. As a starting point there should be nice documentation for the conf directives like the ones found at http://httpd.apache.org/docs-2.0/mod/ for those modules. Among the things I can't find: *) A list of properties to set in the workers.properties (and workers2.properties) *) A list of conf directives (see above) for mod_jk and mod_jk2 *) A list of valves available in tomcat (besides the ones listed in the tomcat javadocs, which are now up again, are there more?) *) Besides valves there is no list of available Engines and Loggers and a whole bunch of other great things that are out there. I found that putting some of the Loggers in my server.xml broken the auto-generator for no apparent reason. I don't know why I have to include: <Realm className="org.apache.catalina.realm.UserDatabaseRealm" debug="0" resourceName="UserDatabase"/> or the autogeneration fails. > I don't mean to rag on you, or the Apache group. ditto > > I know it's all free software and, though it may not sound like it, I am > an appreciative fan, now that I have stumbled onto this list and located > your how-to page. > But I've spent a lot of time fruitlessly searching the > jakarta.apache.org website for answers to my questions and I have found > the doc set taken as a whole to be contradictory, poorly organized, and > in some cases downright misleading. > ditto. Especially since jk contains refrences to jk2, which really confuse me. For example when I start tomcat I see in catalina.out: INFO: Jk running ID=0 time=3/219 config=/usr/local/tomcat/conf/jk2.properties ... and I have no idea why jk would be accessing jk2.properties, or what I can set in there. > > >> My point was that Tomcat is free, and it is developed in the open source >> model. That means the quickest way to get your suggestions >> implemented is >> to do them yourself. But in order to do that, I first need to have a basic knowledge of how things work, which I currently don't. And I can't log into bugzilla to post patches (who do I mail for that?) >> >> The source for the ApacheConfig class is in the Tomcat source bundle, >> where >> it should be. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
