Regarding the document that "apachep2" refers to: Step 4 (which describes the process of building the pieces of mod_jk2) contains something puzzling:
"You will also need to point the apache2.home property somewhere sensible." Why must we have Apache installed on the same machine on which mod_jk2 is built?? I'm trying to run Apache and Tomcat on different machines, but the two seem to be entangled in counter-intuitive ways, as illustrated by the dependence of the mod_jk2 build procedure on Apache. This isn't really a question, just a comment for developers. Newcomers to Tomcat will have fewer confused questions for you if Tomcat is kept orthogonal to other things, like Apache. Clean separations between components make it easier to reason about what's going on. In the present case, there seems to be an implicit assumption that mod_jk2 will be used to connect an Apache and a Tomcat that are both running on the same machine. Wouldn't we be better off without assumptions like this? > -----Original Message----- > From: apachep2 [mailto:[EMAIL PROTECTED] > Sent: Friday, March 14, 2003 10:01 AM > To: 'Tomcat Users List' > Subject: RE: RE : Apache - Tomcat connectors > > > Build: > > Search archive you will find a link to a site that teaches you step by > step how to build mod_jk2. > > Since it's Friday, why don't I just give you the link > > http://www.pubbitch.org/jboss/mod_jk2.html. > > Configure: > > Follow tomcat-connector's document. > > -----Original Message----- > From: LAGALISSE Eric > [mailto:[EMAIL PROTECTED] > Sent: March 14, 2003 12:12 PM > To: Tomcat Users List > Subject: RE : Apache - Tomcat connectors > > I'm not sure that configuring jk2 will be easier if we build > it because > someone can easily build something without knowing how to > configure it. > But i'm ready to believe you so provide us YOUR method to build this > module and i'll write back onto this forum my point of view. > I'm sure a lot of people are waiting for this build method. > > Eric LAGALISSE > > -----Message d'origine----- > De�: apachep2 [mailto:[EMAIL PROTECTED] > Envoy�: vendredi 14 mars 2003 17:43 > ��: 'Tomcat Users List' > Objet�: RE: Apache - Tomcat connectors > > Disagree. I think the simplicity of jk2 configuration (not building of > jk2) confuses people. Because, we as developer, get used to think > complicated. I did feel frustrated building jk2. Once I built > it, I was > surprised that the configuration is so simple. > > -----Original Message----- > From: Dennis Cartier [mailto:[EMAIL PROTECTED] > Sent: March 14, 2003 11:32 AM > To: Tomcat Users List > Subject: RE: Apache - Tomcat connectors > > I agree. I struggled with JK2 for awhile but finally gave up and went > back > to JK. The docs were very confusing and contradictory. I > suppose I could > have appealed for help, but I got the impression that JK2 was still > under > constant change and without being able to be self sufficient, > I felt the > risk was unwarranted. > > Dennis > > -----Original Message----- > From: Chris Dodunski [mailto:[EMAIL PROTECTED] > Sent: Friday, March 14, 2003 7:07 AM > To: Tomcat Users List > Subject: Apache - Tomcat connectors > > > I'm honestly astounded at the number of people struggling with > successfully > installing and configuring Apache - Tomcat connectors. An extensive > search > of apache.org (and other sites) reveals why. Documentation is vague, > fragmented, and quite frankly confusing. It's frustrating > and it's time > wasting. Time I say for some clear, concise, blow by blow > documentation > on > performing what should be a relatively simple procedure. Do > you agree? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
