RE: compiling mod_jk 2.0.4 on macos X (10.2)
Hi Marco, It sounds like the configure script is telling Make (*simplification*) to only build static files (.la), which is bizarre. Try running configure with the following option to force it to build the shared (.so) libraries: ./configure --enable-shared=yes ... *plus other options as usual* Then do: make clean make as usual. Hope that helps, Adam. -Original Message- From: Marco Baringer [mailto:[EMAIL PROTECTED] Sent: 02 April 2004 15:03 To: [EMAIL PROTECTED] Subject: compiling mod_jk 2.0.4 on macos X (10.2) i'm trying to compile mod_jk (just the apache side, not the tomcat side). I downloaded jakarta-tomcat-connectors-jk2-2.0.4-src. apr-0.9.4 and apr-util-0.9.4 and was able to successfully run configure (i'm building against apache 1.3). however trying to do make results in an error about build/jk2/apache13/mod_jk2.so not existing (it doesn't). i have all the .o files and i have mod_jk2.a and mod_jk2.la, why isn't the .so file being built? Attempts to build against apache2 result in configure errors about libapr not being found. -- Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ This email and any files attached is intended for the addressee only and may contain information that is confidential and/or legally privileged. Unauthorised use is strictly prohibited and may be unlawful. If you are not the addressee, you should not read, copy, disclose or otherwise use this message, including any attachment, except for the purpose of delivery to the addressee. We make every effort to keep our network free from viruses. However, you do need to verify this e-mail and any attachments to it to be virus free as we can take no responsibility for any computer virus which might be transferred by way of this e-mail. Scanning of this message and addition of this footer is performed by SurfControl E-mail Filter software in conjunction with virus detection software. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connectors makefile typo...
Hello guys,
I have found a bug in the Makefile. Not sure whether to put this in the bug
DB as its a problem with the make file and not the connectors. Apologies if
I shouldn't have posted here. Here's the problem below, anyway.
I downloaded the connectors tar.gz
(jakarta-tomcat-connectors-jk2-src-current.tar.gz version 2.0.2) and went
into jk/native2 to build the thing.
I used the instructions Kurt/Henri posted to dev (couldn't get the one in
README.txt working). I basically did the following:
./configure --with-apxs2=/usr/sbin/apxs
make
This failed miserably due to a problem in the server/apache2/Makefile make
file. This is the error output form the original try:
...
/usr/bin/ld: cannot find -lapr-0
collect2: ld returned 1 exit status
make[1]: *** [../../../build/jk2/apache2/jkjni.la] Error 1
make[1]: Leaving directory
`/root/work/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/server/apache
2'
make: *** [jk2-build] Error 1
The problem is on line 37 as follows:
JK_LDFLAGS=-L${APACHE2_LIBDIR} -lcrypt -lapr-0
Obviously the -lapr-0 should read -lapr -0. I fixed this and re-ran make and
all was lovely.
Thought you'd want to know. If you need anymore info, please feel free to
e-mail.
Adam.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/jk/native2 BUILD.txt
Ah excellent. I was wondering why my build was failing miserably. Adam (formerly [EMAIL PROTECTED], not been on in a year or so) -Original Message- From: Kurt Miller [mailto:[EMAIL PROTECTED] Sent: 19 March 2004 17:22 To: Tomcat Developers List Subject: Re: cvs commit: jakarta-tomcat-connectors/jk/native2 BUILD.txt Hi Henri, I hope you don't mind, but I rewrote the build instructions for Unix-like systems. If its OK with you I'd like to commit this (or something like it). Of course comments, additions or criticisms welcome too. ;-) -Kurt Information on building mod_jk2: Starting with 2.0.4, APR is mandatory for jk2. For Apache 2.0 or greater jk2 will use APR that was used to build Apache 2.0. For Apache 1.3, jk2 must build APR and APR_UTIL from source. DSO build instructions for Unix-like systems: The compiler used to build jk2 must match the one used to build Apache. You may need to set an environment variable before configuring such as CC=cc. `apxs -q CC` will tell you what compiler was used for Apache. The most straightforward way to configure jk2 is to use apxs that comes with Apache. Linux distributions may need to have additional rpm's installed such as Apache2 devel rpm, httpd-devel or apache2-devel or for Apache 13, Apache devel rpm, httpd-devel or apache-devel depending on your distribution. Example Apache2 build and install: cd jakarta-tomcat-connectors/jk/native2 ./configure --with-apxs2=/your/path/to/apxs make cd ../build/jk2/apache2 apxs -n jk2 -i mod_jk2.so Example Apache13 build and install: apr and apr-util will be configured and built for you while configuring and building jk2. There is no need to separately configure and build them. cd jakarta-tomcat-connectors/jk/native2 ./configure --with-apxs=/your/path/to/apxs \ --with-apr=/your/path/to/apr-source \ --with-apr-util=/your/path/to/apr-util-source make cd ../build/jk2/apache13 apxs -n jk2 -i mod_jk2.so NOTE: pthread support may be automatically detected and built into apr. If apache13 was not built with pthread support, you can either disable it by adding --disable-apr-threads while configuring, or load the pthread library in httpd.conf using the LoadFile directive. Optional configure arguments (for 1.3 and 2.0): If you want to have JNI support, add --with-jni and be sure to have the JAVA_HOME environment variable point to your Java Environment. This will build inprocess jni support into mod_jk2.so and additionally build libjkjni.so. libjkjni.so can be used by tomcat to provide support for channel unix and should be installed in the apache libexec dir. Use `apxs -q LIBEXECDIR` if you are unsure of its location. Libjkjni.so will be located in the same directory as mod_jk2.so after building with this option. If you want to have PCRE (Perl Compatible Regular Expressions) support for jk2 uri directives, add --with-pcre while configuring. - 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]
Re: HELP ! building mod_jk with fdatasync...
# #worker.tomcat.cachesize=ajp13 # # worker.tomcat.lbfactor=100 # # Load Balancer worker # # worker.loadbalancer.type=lb # worker.loadbalancer.balanced_workers=tomcat1,tomcat2 # END Then you must change httpd.conf with this instructions: LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c # # Configure mod_jk # JkWorkersFile /usr/local/apache/conf/workers.properties JkLogFile /usr/local/apache/logs/mod_jk.log JkLogLevel info Now you must do apachectl stop and apachectl start. If you apache is up, mod_jk is right! With Apache and two-three tomcat-istances is possible to do 'load balancing'. We also must install Cocoon for its XML support. To thank Open Source for its work and research, my company offers mod_jk.so in a tar distribution (mod_jk_solaris26.tar.gz) if will receive a simple e-mail to: [EMAIL PROTECTED] or [EMAIL PROTECTED] Best Regards. -- | Adam Fowler | | Third year undergraduate | TomcatBook Project | | Computer Science | Author and Administrator | | University of Wales, Aberystwyth | http://tomcatbook.sourceforge.net| | Web: http://users.aber.ac.uk/aff9 | [EMAIL PROTECTED] | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[DOC] TC4 jakarta doc site...
Hi guys, I just upgraded to Mozilla 0.9 and tried having a look at the Server Configuration part of the tc4 doc site. (I hope to have my tc4 appendix shelled out by the end of the day.) I noticed that the background on the left is set to black...Problem is, the styles your using don't seem to be valid as the text comes out black too. (Spotted the problem yet!?! 8o) ) Also, a black background is a bit gash! (call me old fashioned) Mozilla works fine with my XHTML site which uses CSS 1 and 2 so I think it may be your site. I can get by without it, but as you can tell its not exactly ideal! Adam. -- Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Tomcatbook Project Author and web maintainer http://tomcatbook.sourceforge.net web: http://users.aber.ac.uk/aff9 e-mail: [EMAIL PROTECTED] --
Re: [DOC] TC4 jakarta doc site...
Rob, If I could get CVS access behind this damned secure network I'd volunteer!...Unless you'd let me FTP/SSH to it 8o) Tomcat can have my thoroughly tested layout if you'd like though. (With a few mods, of course!) Take a gander at http://tomcatbook.sourceforge.net Adam. Rob S. wrote: I submitted a mockup site several weeks ago, and a modified home page using the same sort of scheme yesterday. I don't think people like to comment on aesthetics =) Problem is that everyone has a friend of a friend that will make us a sharp, light-weight site, but no one ever gets around to it =/ - r -Original Message- From: Adam Fowler [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 21, 2001 11:56 AM To: [EMAIL PROTECTED] Subject: [DOC] TC4 jakarta doc site... Hi guys, I just upgraded to Mozilla 0.9 and tried having a look at the Server Configuration part of the tc4 doc site. (I hope to have my tc4 appendix shelled out by the end of the day.) I noticed that the background on the left is set to black...Problem is, the styles your using don't seem to be valid as the text comes out black too. (Spotted the problem yet!?! 8o) ) Also, a black background is a bit gash! (call me old fashioned) Mozilla works fine with my XHTML site which uses CSS 1 and 2 so I think it may be your site. I can get by without it, but as you can tell its not exactly ideal! Adam. -- Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Tomcatbook Project Author and web maintainer http://tomcatbook.sourceforge.net web: http://users.aber.ac.uk/aff9 e-mail: [EMAIL PROTECTED] --
Re: JDK 1.3.0...
On Tuesday 17 July 2001 22:46, you wrote: You do realize that re-distribution of the JDK is illegal, right? You can only redistribute the JRE. Oh F*?*!!! *phoning Paul* Thx Jon. Adam. -- - | Adam Fowler | | Help Desk Live Project| TomcatBook Project| | Information Services | Author and Web Maintainer | | University of Wales, Aberystwyth | http://tomcatbook.sourceforge.net | | Web: http://users.aber.ac.uk/aff9 | E-mail: [EMAIL PROTECTED] | -
Re: [DOC] TC4 jakarta doc site...
Hi, Change it to Air force blue 8o) wedgewood blue as its called over here. Not that I'm bias! *dreamin' of harrier pilotage* Adam. Pier P. Fumagalli wrote: Adam Fowler at [EMAIL PROTECTED] wrote: I noticed that the background on the left is set to black...Problem is, the styles your using don't seem to be valid as the text comes out black too. (Spotted the problem yet!?! 8o) ) Also, a black background is a bit gash! (call me old fashioned) Downloaded it for OS/X (seems to work fairly well now, 0.9.2 as of today's nightly!) and I have the same problem... It's not THAT black (seen on a LCD of my Titanimu), but definitely too dark... Might want to change that sky blue background into something slightly less dark? Pier
Re: [DOC] INSTALL.txt
Hi, I'm gonna follow your doc to install tomcat 4 on mandrake tonight. I'll make change to it for *nix platforms and highlight them then e-mail you the revised copy 8o) Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Wednesday 18 July 2001 00:23, you wrote: Along the right line? Used the formatting from the TC4 readme files. Needs some polish. - r Content-Type: text/plain; charset=iso-8859-1; name=INSTALL.txt Content-Transfer-Encoding: quoted-printable Content-Description:
Re: [DOC] INSTALL.txt
Wow, that was quick 8o) Always a good thing with install instructions! Here's the update INSTALL.txt Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Wednesday 18 July 2001 21:58, you wrote: Hi, I'm gonna follow your doc to install tomcat 4 on mandrake tonight. I'll make change to it for *nix platforms and highlight them then e-mail you the revised copy 8o) Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Wednesday 18 July 2001 00:23, you wrote: Along the right line? Used the formatting from the TC4 readme files. Needs some polish. - r Content-Type: text/plain; charset=iso-8859-1; name=INSTALL.txt Content-Transfer-Encoding: quoted-printable Content-Description: -- Apache Tomcat Version 4.0 Beta 6 Install Guide = cvs keyword thing INTRODUCTION: Welcome! This document explains how to perform a stand-alone installation of the Tomcat 4.0 servlet container. Once you're up and running, you will have access to the more detailed documentation locally via Tomcat's default home page, as well as administration and sample applications. As well, the documentation is available locally at: $CATALINA_HOME/webapps/docs/index.html where $CATALINA_HOME is the root of the directory you extracted the Tomcat files to. The absolute latest version of the documentation is always available online at the following URL: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/index.html Because the documentation released with each version of Tomcat is the latest as of that release, there is a good chance the online documentation will be slightly updated. NOTE: It is STRONGLY reccomended that you complete this minimal, stand-alone installation before continuing on to more advanced topics. === DOWNLOADING: === In the rare occurence that you find yourself reading this file without a copy of Tomcat 4 to install, you can obtain the latest version here http://jakarta.apache.org/site/binindex.html == INSTALLING: == Fortunately, installing the Tomcat servlet container consists of a few, easy steps: extract the archive, and set environment variables. Of course, since Tomcat is written in Java, it is assumed that you have install at least version 1.2 of the JDK. You can download the JDK from Sun at the following URL http://java.sun.com/j2se/ 1) Unpack the files You've most likely completed this step already =) Lets say that for installation (A), you're on a Windows machine and you've unpacked the files to C:\tomcat Or for installation (B) on a *nix machine, you've unpacked it to /usr/local/tomcat cd /var (I thought TC should go in /var for most platforms???) mv tomcat-download-file /var/ tar xzvf jakarta-tomcat-4.0-br.tar.gz OR unzip jakarta-tomcat-4.0-br.tar.Z tar xvf jakarta-tomcat-4.0-br.tar 2) Set your environment variables Tomcat 4 requires 2 environment variables: CATALINA_HOME and JAVA_HOME. CATALINA_HOME should be set to the root of your Tomcat installation, and JAVA_HOME should be set to the root of your JDK installation. For the Win9X-series of operating systems, add the following lines to your C:\AUTOEXEC.BAT file: SET CATALINA_HOME=C:\tomcat SET JAVA_HOME=C:\jdk1.3.1 In WinNT-based systems, you modify environment variables by first right- clicking on the My Computer icon, and going to Properties. In NT you get to the properties by doing THIS, and in 2000, by doing THIS. For *nix, is there any different for the different shells? I'm no *nix expert by any means =) export CATALINA_HOME=/var/jakarta-tomcat-4.0-b5 export JAVA_HOME=/usr/java/jdk1.3 NB This should either be done in a systemV startup script or /etc/profile to make it system wide. (Preferably startup script so its available on tomcat start on boot if required) 3) Start it To start the container, execute the script appropriate to your operating system. The startup and shutdown scripts are named appropriately, and found in $CATALINA/bin. For *nix, that will be the scripts ending with the sh extension, and for Windows, bat. cd
[DOC] INSTALL.txt and Init Script...
Hey all, I've updated my initialisation script. Installation details are in the file. I also forgot to mention in my last post with regards to the nice INSTALL.txt 8o) that a symbolic link should be made like:- ln -s /var/jakarta-tomcat-4.0-b5/ /var/jakarta-tomcat So to allow easy upgrades. This is also detailed in the tomcat script (attached) Hope this helps. Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] tomcat systemV init script
Re: [DOC] TOC - thoughts
Yup that's correct. It does work OK with 8.0 + Thanks for the fix - I'll put it on my site. Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Friday 13 July 2001 08:24, you wrote: Putting little notes about things like the JDK 1.3.1 linux issue are VERY useful. I hate it when M$ have docs that don't mention things such as none of your data is encrypted, by the way JDK 1.3.1 problems with recent glibc could be fixed by adding : export LD_ASSUME_KERNEL=2.2.5 IBM JDK 1.3 works perfectly under Redhat 7.1 (may be also MDK 8.0) --
Re: [DOC] TOC - thoughts
Hi Everyone on the TomcatBook project (Hitchhiker's guide to tomcat 8o) ) are using DocBook too. ATM we are only producing an appendix for tomcat 4 (Well, I am) but I would like to see it evolve into a separate Document. The reason it is only an appendix ATM is that 4.0 hasn't been deployed widely like 3.2.x yet. So my job is detailing all of the differences in configuration and deployment. There is a list of authors for TomcatBook at http://sourceforge.net/docman/?group_id=26042 As I say, I'm the only Tomcat 4 guy ATM. I'd be glad to work with you on this and share thoughts etc. If you'd like. Is this documentation going to be used on the jakarta-tomcat site? If so who can commit the documents? Also, TomcatBook are using the GNU FDL so if apache's license is more restrictive that could be a problem (why documentation is covered by apache's software license I don't know!) I know Alex on the tomcat-dev list is also doing documentation. My advice is to also go and join tomcatbook at groups.yahoo.com/group/tcbook as this is a good place to ask questions about such things. Do you know of a good editor for DocBook? I know AbiWord should do it. I also have the task of converting our projects docs to html for our site (http://tomcatbook.sourceforge.net) and am using jboss. I'm having issue with converting someon's build.bat file to a nice build.sh file though. Any help is much appreciated. I have a mandrake 8.0 machine here with tc 4 installed and am currently working on getting it communicating with apache 1.3.x then once that is working i'll switch to 2.0 and get info on that. Drop me a line with your thoughts either on tomcat-dev or at [EMAIL PROTECTED] Regards, Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Friday 13 July 2001 21:49, you wrote: hello adam, i am planning to use docbook, and i will post my first *.tar.gz file containing the tomcat documentation next week on [EMAIL PROTECTED] mailing list. i am currently working on making the following... - Preface - Authors (I need some info and help on this, such as who to put inc. me) - Admin Guide. Once the admin guide is done, i will start to work on the developer's guide, cause the admin guide is kinda more important. To just clear things off, i am working on the Tomcat 4.0 documentation, while other might be working on the Tomcat 3.2/.3 documentation, the reason is, that tomcat4 is going to be the next major release; so its better if i and a couple of others start preparing tomcat4 documentation. The following are the specifications of the document. 1)It is a manual, that it contains three books (part I,II,III respectively). The three are admin guide, dev. guide and application developer's guide. 2)I am making it with DocBook XML 4.1.2. I am producing two layouts at the moment, which are: .PDF and .HTML, including .txt as well. 3)Some people told me that to work with Anakia DTD but i have been working with DocBook for roun bout three years, and i am quite used to it; so if anyone would like to convert it to different formats, i will pass the Documentation source to them, so they can keep the anakia version. as well as i am producing an .xhtml transformation as well, so it will be easier for people using anakia to convert it. 4)I am very confused about how to arrange the authors and collaborators list because i dont want anyone who has contributed to be left out in any manney, nor would they like it. so i need some help on that as well. 5)Can i change the docbook stylesheet to accept my own coloring information?. Thanx in advance. Hiten Pandya (15) [EMAIL PROTECTED] Open to suggestions as always... --- From: Adam Fowler [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [DOC] TOC - thoughts Date: Wed, 11 Jul 2001 17:38:58 + MIME-Version: 1.0 Received: from [64.208.42.41] by hotmail.com (3.2) with ESMTP id MHotMailBD17B73600734004319E40D02A29087A0; Thu, 12 Jul 2001 20:34:14 -0700 Received: (qmail 15256 invoked by uid 500); 13 Jul 2001 03:12:01 - Received: (qmail 10554 invoked from network); 11 Jul 2001 16:39:06 - From tomcat-dev-return-24412-h_pandya5 Thu, 12 Jul 2001 20:34:56 -0700 Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk list-help: mailto:[EMAIL PROTECTED] list-unsubscribe: mailto:[EMAIL PROTECTED] list-post: mailto:[EMAIL PROTECTED] Delivered-To: mailing list [EMAIL PROTECTED] Delivered-To: moderator for [EMAIL PROTECTED] X-Mailer: KMail [version 1.2] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Putting little
Re: [DOC] Vote on oustanding doc issues?
Ah-ha! the culprit!!! 8o) Adam. On Friday 13 July 2001 03:36, you wrote: Adam Fowler at [EMAIL PROTECTED] wrote: *being random* The RPM of tc4 worked great on Mandrake 8.0 beta 3. Incidentally, the tc4 docs suck. I had to read deeply into the config files to find out how to get it working with apache. This is fine for a seasoned admin, but the general web community wouldn't have a clue (By that I refer to the quantity of mails in tomcat-user!) 8o) We could do with better tc4 docs. If you're talking about how to set up tomcat with apache, that's my fault :) Pier
Re: [DOC] TOC - thoughts
Putting little notes about things like the JDK 1.3.1 linux issue are VERY useful. I hate it when M$ have docs that don't mention things such as none of your data is encrypted, by the way Not that I'm bitter 8o) Adam. On Wednesday 11 July 2001 14:58, you wrote: Christopher Cain wrote: Rob S. wrote: [snip] First off, I think we should have an ultra-quick install guide. If you're like a lot of geeks, you know your stuff. You need to know a quick few steps, a quick 2-3 gotchas, and BAM that's it. I want to make sure the quick-and-dirty impatient install is available to the people who can take advantage of it; admins experienced with other containers, trying Tomcat for the first time perhaps. +1 PI.2.1: I love pictures! Some nice diagrams in here would go a lllong way. Not sure about the choose OS or install Java sections. I mean, there's catering to the LCD and there's catering to the LCD... I haven't yet had a chance to look over the TOC (planning on doing it tonight), but one of the docs I have lying around is a step-by-step on installing java on Linux *specifically* in preparation for a Tomcat build/install. Granted, the README file hits the important stuff, like what needs to be in the CLASSPATH, etc. I was actually thinking of morphing it into a more general (and quick) guide to preping your OS for a Tomcat build/install (I have some Windoze notes lying around as well). I could very quickly touch on Java installation, including a few Linux-specific tips above and beyond the rather obvious actual install, cover the environment varibles that need to be defined for a build, reiterate the jakarta directory structure that needs to be in place, etc. Basically, everything up to the point of the actual build. That would be great, and that's pretty much what the TOC outlines (though not in that detail). The problem with having OS-specific quick-and-dirty install guides is that if one aspect changes, the separate guides get out of sync. I'd suggest you clearly divide the following three parts: - Pre-install - Standalone install - Integrating with Web server Since that's the structure I'm using in the major parts of the Install Guide of the TOC. Well, my thoughts on the aforementioned doc I was planning are to provide a list of the available JDKs for each platform, what else one needs to download for certain optional functionality (SSL, etc.), where to get each of them, and any relevant comments on software selection. Mainly just the huge stuff, like the infamous Sun 1.3.1 JDK for Linux completely broken under the new gcc threading libraries. (That one really pissed me off.) This might fall under the category of too much information as Rob is stating, but my feeling is that it is easy enough to skip over entire sections (assuming they're laid out logically) in a Preping your OS for Tomcat doc, and those users who are planning on building out a new box (or reformatting an existing box) specifically for a web server will appreciate such heads-up info. Getting Tomcat up and running on a barebones OS install is pretty rare for us developers, but it happens quite frequently in the corporate world. The bigger the master Tomcat documentation library, from the essentials to the sublimely tangential steps along the way, the more comfortable corporations will feel about choosing Tomcat over a proprietary solution. As long as someone is willing to write such things, which in this case I am, why not just throw it in the mix for the few people who might benefit from it? Of course, I completely agree that there also needs to be some short-and-sweet versions of how to do install-type things, so maybe an abbreviated version of my Preping doc would also be in order. I like it. Please see how it would fit in with the proposed pre-install / standalone install chapters.
Re: [DOC] Vote on oustanding doc issues?
*being random* The RPM of tc4 worked great on Mandrake 8.0 beta 3. Incidentally, the tc4 docs suck. I had to read deeply into the config files to find out how to get it working with apache. This is fine for a seasoned admin, but the general web community wouldn't have a clue (By that I refer to the quantity of mails in tomcat-user!) 8o) We could do with better tc4 docs. Just sticking my neb in - I think a separate tree for 3.2+3.3 would be a bit unnecessary. Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Wednesday 11 July 2001 15:26, you wrote: Craig R. McClanahan wrote: On Mon, 9 Jul 2001, Alex Chaffee wrote: Bundle the 3.2.x docs with 3.2.x and only have the 3.3 docs online (latest Tomcat release). If you want the 3.2.x docs, get them with the binary or whatever. I certainly don't think we should keep old versions of documentation updated. I mean, why would updated 3.0 or 3.1 docs be useful? Unless and until there's a 3.3 or 4.0 final release, *3.2* is the latest Tomcat release, and deserves to be documented on the web site. OK, but my point is that as we improve the 3.x docs -- regardless of the value of x -- the 3.2 docs will become less relevant. Right now there are many differences between the 3.2 and 3.3 docs, but they're mostly in the connector docs, which AFAIK haven't changed much if at all in operation. This leads me to conclude that the docs in the 3.3 tree are just as valid when applied to 3.2, except that they're better docs, since more people have had a chance to revise them. That's why I'd like to remove the Tomcat 3 docs that happened to be in the depot at the time 3.2 shipped in favor of the latest version of the Tomcat 3 docs (which happen to be in the 3.3 dev tree). Perhaps the easiest way to do this would be with a separate depot. I'm shying away from that for the reasons you (Craig) brought up. It's nice for docs to be in the same depot as the code... There's no reason to banish the current Tomcat released version, or any other version that is being actively developed. And it's quite easy to arrange the user interface so that it's obvious which version you are looking at (for example, including Tomcat X.Y in the header or footer of the pages about that version). Again, apart from 3 vs 4, the difference between versions 3.2 and 3.3 is small, as far as docs are concerned, so announcing Tomcat 3.2 in the header wouldn't be very salient, and would just promote forking of docs. We seem to be in this quandary because the docs have not really been part of the release process -- they get released slapdash relative to the code milestones. By the way, it seems like the majority of the existing documentation is about installation. If there were a clean, robust install script, it would remove 90% of the text on the site. Maybe before we write (rewrite) install docs we should write an install script. I know that was on your todo list for 4 -- how's that coming?
Re: RPM
Damnit! Can't remember. Ask Henri Gomez. Adam. At 14:08 14/06/2001 +0200, you wrote: Hello. Where can I find java and tomcat *.rmp packages? regards, Margus Hein Adam Fowler Second year Computer Science undergraduate University of Wales, Aberystwyth e-mail: [EMAIL PROTECTED] web: http://gucciboy.dyndns.org/aff9 Every new beginning comes from some other beginning's end
RE: mod_jk for Apache 1.3.17
Hi, Lots of people have been having trouble with the standard downloadable binaries not working lately. You may need to recompile it for your machine. I'm not sure of how to do this in Win32. Try downloading the source (from the jakarta website) and going to src/native/apache1.3/ and opening the workspace there in Visual Studio 6 and compiling it. Hope this helps. Regards, Adam. Adam Fowler Second year Computer Science undergraduate University of Wales, Aberystwyth Carroll College, WI, USA(2000-2001) web: http://gucciboy.dyndns.org/aff9 e-mail: [EMAIL PROTECTED] "Every new beginning comes from some other beginning's end" -Original Message- From: Pilho Kim [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 24, 2001 5:42 PM To: [EMAIL PROTECTED] Subject: Re: mod_jk for Apache 1.3.17 It doesn't work with Apache 1.3.17. On Sat, 24 Feb 2001, Dave Oxley wrote: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.1/bin/win32/i38 6/mod_jk.dll Hi, I need mod_jk for Apache 1.3.17 Tomcat 3.2.1 on NT 4.0. Where can I get it? Thanks in advance, Kim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
