RE: Documentation ... : Your Advices please
I think most people would probably use later versions of both Java and Tomcat if they were going to set an environment up from scratch now. So I would suggest it better for you to upgrade now and document for later releases. Rgds -Original Message- From: Raghupathy,Gurumoorthy [mailto:[EMAIL PROTECTED] Sent: 22 June 2005 09:14 To: 'Tomcat Users List' Subject: Documentation ... : Your Advices please Hello All, I am thinking of writing a document of how to set up. Apache + tomcat + mod_jk with Apache using SSL. for free. I am using Apache 1.3.* and Tomcat 4.1 and this works very nicely I have this running on my linux box for 2 years + now. I need your advice if I create a document of how to setup this will it be use full. I am thinking that tomcat now being 5.5.* and apache 2.0.* will it be worth my time for the peoplpe or do you think I should upgrade as well Regards Guru Gurumoorthy Raghupathy EMFS - Fidelity Investments International * Tel: +44 1737 836798 * Internal: 8-724 6798 * Tel (R): +442086423806 * Mail-Zone : XTB2B * E-Mail: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Regret for the things we did can be tempered by time; it is regret for the things we did not do that is inconsolable Important: Fidelity Investments International, Fidelity Investment Services Limited, Fidelity Pensions Management and Financial Administration Services Limited (a Fidelity Group company) are all authorised and regulated in the UK by the Financial Services Authority and have their registered offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144. Fidelity only gives information on products and does not give investment advice to private clients based on individual circumstances. Any comments or statements made are not necessarily those of Fidelity. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any computer. All e-mails sent from or to Fidelity may be subject to our monitoring procedures. 'Direct link to Fidelitys website. http://www.fidelity-international.com/world/index.html http://www.fidelity-international.com/world/index.html ***Disclaimer*** The contents of this Email may be privileged and are confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Should you wish to use Email as a mode of communication, CMi plc and its subsidiaries are unable to guarantee the security of Email content outside of our own computer systems. This footnote also confirms that this Email message has been checked by MIMESweeper for the presence of computer viruses. Whilst we run anti-virus software, you are solely responsible for ensuring that any Email or attachment you receive is virus free. We disclaim any liability for any damage you suffer as a consequence of receiving any virus. Checkmate International plc (CMi) Registered in England No: 1899857 Registered Office 4th Floor, 35 New Bridge Street, London, EC4V 6BW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Documentation
Hi, Where can I find documentation about Tomcat looger, and debug verbosity params? I change the debug and verbosity values, and the log is always the same. Different Tomcat versions have different ways to configure logging. Make sure you're looking at the documentation for your Tomcat version. The verbosity attribute is mostly for Tomcat 3.x. The debug attribute, if allowed (the docs will list it if it's allowed), goes from 0 (the default, no logging) to 99 (the highest, max logging). But it's mostly used in Tomcat 4.x, and less in 5.x. The more recent versions of Tomcat use Commons-Logging increasingly. To configure their logging, you need to pick an implementation (e.g. log4j or JDK 1.4 logging) and configure Tomcat to use that logging implementation with your chosen logging levels. This is explained in the FAQ and documentation (the latter only for Tomcat 5.5). For Tomcat 5.5, there's no Logger, and no debug attributes, at all. It's all Commons-Logging. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Documentation
Thanks Yoav, Maybe, I don't explain very well my case. For example, If I active the debug in the database pool connection, can I see the active connection, free connection, the queries, etc... Other example, I'm configuring a cluster in memory, I would like activate the debug option, in order to know if the machines of the cluster is working good or not. I mean, I looking for this documentation, but I find nothing about that. Do you know if are there any documentation about this issues?? Thank a lot. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: martes, 07 de diciembre de 2004 19:40 To: Tomcat Users List Subject: RE: Documentation Hi, Where can I find documentation about Tomcat looger, and debug verbosity params? I change the debug and verbosity values, and the log is always the same. Different Tomcat versions have different ways to configure logging. Make sure you're looking at the documentation for your Tomcat version. The verbosity attribute is mostly for Tomcat 3.x. The debug attribute, if allowed (the docs will list it if it's allowed), goes from 0 (the default, no logging) to 99 (the highest, max logging). But it's mostly used in Tomcat 4.x, and less in 5.x. The more recent versions of Tomcat use Commons-Logging increasingly. To configure their logging, you need to pick an implementation (e.g. log4j or JDK 1.4 logging) and configure Tomcat to use that logging implementation with your chosen logging levels. This is explained in the FAQ and documentation (the latter only for Tomcat 5.5). For Tomcat 5.5, there's no Logger, and no debug attributes, at all. It's all Commons-Logging. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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: Documentation
if you want to see cluster output, just configure debug for org.apache.catalina.cluster using log4j for example to setup log4j all I did was to add log4j.xml into common/classes and log4j.jar into common/lib Filip - Original Message - From: Pablo Carretero [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 1:34 PM Subject: RE: Documentation Thanks Yoav, Maybe, I don't explain very well my case. For example, If I active the debug in the database pool connection, can I see the active connection, free connection, the queries, etc... Other example, I'm configuring a cluster in memory, I would like activate the debug option, in order to know if the machines of the cluster is working good or not. I mean, I looking for this documentation, but I find nothing about that. Do you know if are there any documentation about this issues?? Thank a lot. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: martes, 07 de diciembre de 2004 19:40 To: Tomcat Users List Subject: RE: Documentation Hi, Where can I find documentation about Tomcat looger, and debug verbosity params? I change the debug and verbosity values, and the log is always the same. Different Tomcat versions have different ways to configure logging. Make sure you're looking at the documentation for your Tomcat version. The verbosity attribute is mostly for Tomcat 3.x. The debug attribute, if allowed (the docs will list it if it's allowed), goes from 0 (the default, no logging) to 99 (the highest, max logging). But it's mostly used in Tomcat 4.x, and less in 5.x. The more recent versions of Tomcat use Commons-Logging increasingly. To configure their logging, you need to pick an implementation (e.g. log4j or JDK 1.4 logging) and configure Tomcat to use that logging implementation with your chosen logging levels. This is explained in the FAQ and documentation (the latter only for Tomcat 5.5). For Tomcat 5.5, there's no Logger, and no debug attributes, at all. It's all Commons-Logging. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
RE: Documentation
Hi, Maybe, I don't explain very well my case. For example, If I active the debug in the database pool connection, can I see the active connection, free connection, the queries, etc... There are two ways to determine what logging output you will see if you enable debug-level logging for a given Tomcat component. One way to is try it. The other way is to look at the source code, which of course is freely available for you to download and examine. If you look at the source, you will see that some components do more logging than others. So even setting debug-level logging for them might not yield much information. As to the specific question above about database pooling: because that's not implemented by Tomcat, but by a pluggable implementation (DBCP by default), it's up to the implementation's logging. Again, you can try it, or you can consult the DBCP source code. Alternatively you can plug in your own connection pooling implementation. I mean, I looking for this documentation, but I find nothing about that. Do you know if are there any documentation about this issues?? What are you asking is generic. Documentation for Tomcat's own logging is covered under the Logger configuration reference and, for Tomcat 5.5, in the logging-howto section of the docs. There is also a FAQ entry showing how to configure Tomcat 5.0.x with log4j. For parts of the code that are not Tomcat's own, e.g. DBCP, you need to consult that component's documentation. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Documentation
Yoav and Filip, thanks a lot. I'm very new in the Open Source software, I good like the idea, and under my point of view, is the best solution event the big companies. But for beginner, is very difficult. Thank you very much I try continue with your indication. Best regards. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: martes, 07 de diciembre de 2004 20:37 To: Tomcat Users List Subject: RE: Documentation Hi, Maybe, I don't explain very well my case. For example, If I active the debug in the database pool connection, can I see the active connection, free connection, the queries, etc... There are two ways to determine what logging output you will see if you enable debug-level logging for a given Tomcat component. One way to is try it. The other way is to look at the source code, which of course is freely available for you to download and examine. If you look at the source, you will see that some components do more logging than others. So even setting debug-level logging for them might not yield much information. As to the specific question above about database pooling: because that's not implemented by Tomcat, but by a pluggable implementation (DBCP by default), it's up to the implementation's logging. Again, you can try it, or you can consult the DBCP source code. Alternatively you can plug in your own connection pooling implementation. I mean, I looking for this documentation, but I find nothing about that. Do you know if are there any documentation about this issues?? What are you asking is generic. Documentation for Tomcat's own logging is covered under the Logger configuration reference and, for Tomcat 5.5, in the logging-howto section of the docs. There is also a FAQ entry showing how to configure Tomcat 5.0.x with log4j. For parts of the code that are not Tomcat's own, e.g. DBCP, you need to consult that component's documentation. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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: Documentation
Hi, No problem. We're glad to help, and you should feel free to ask questions. That's why these mailing lists are here, and I think these lists and forums are one of the better assets of open-source software. Many paid support organizations have neither the expertise nor the enthusiasm found on this list. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Pablo Carretero [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 3:01 PM To: 'Tomcat Users List' Subject: RE: Documentation Yoav and Filip, thanks a lot. I'm very new in the Open Source software, I good like the idea, and under my point of view, is the best solution event the big companies. But for beginner, is very difficult. Thank you very much I try continue with your indication. Best regards. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: martes, 07 de diciembre de 2004 20:37 To: Tomcat Users List Subject: RE: Documentation Hi, Maybe, I don't explain very well my case. For example, If I active the debug in the database pool connection, can I see the active connection, free connection, the queries, etc... There are two ways to determine what logging output you will see if you enable debug-level logging for a given Tomcat component. One way to is try it. The other way is to look at the source code, which of course is freely available for you to download and examine. If you look at the source, you will see that some components do more logging than others. So even setting debug-level logging for them might not yield much information. As to the specific question above about database pooling: because that's not implemented by Tomcat, but by a pluggable implementation (DBCP by default), it's up to the implementation's logging. Again, you can try it, or you can consult the DBCP source code. Alternatively you can plug in your own connection pooling implementation. I mean, I looking for this documentation, but I find nothing about that. Do you know if are there any documentation about this issues?? What are you asking is generic. Documentation for Tomcat's own logging is covered under the Logger configuration reference and, for Tomcat 5.5, in the logging-howto section of the docs. There is also a FAQ entry showing how to configure Tomcat 5.0.x with log4j. For parts of the code that are not Tomcat's own, e.g. DBCP, you need to consult that component's documentation. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Documentation
On Tue, Dec 07, 2004 at 09:01:07PM +0100, Pablo Carretero wrote: : I'm very new in the Open Source software, I good like the idea, and under my : point of view, is the best solution event the big companies. But for : beginner, is very difficult. I'd argue that just about any software -- commercial or otherwise -- can be difficult to grasp in the early days. J2EE? Systems administration? Oracle? The list goes on and on... -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: documentation for ant tasks
Hi, The Manager How-To has some ant details. It has a lot of detail on the actual Manager tasks (the same whether invoked from Ant or from the web browser), which is probably what you want. The actual Ant tasks don't have any logic, they're just convenience wrappers for invocation via Ant. Yoav Shapira Millennium Research Informatics -Original Message- From: Jeff Ousley [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 6:18 PM To: [EMAIL PROTECTED] Subject: documentation for ant tasks hello! is there anyplace where the catalina ant functions/tasks are documented? i've searched but obviously i'm not looking in the proper place. thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: documentation on installing two instances of tomcat
Hi, Here's some: - Download tomcat .zip - Unpack first installation to a directory of your choice, ports will be 8080 and 8005 by default - Unpack second installation to a different directory of your choice - Edit conf/server.xml of the second installation to something other than 8005 and 8080, say 8006 and 8081. - That's it. Yoav Shapira Millennium Research Informatics -Original Message- From: Yoo, Joon [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 10:55 AM To: ([EMAIL PROTECTED]) Subject: documentation on installing two instances of tomcat Is there any documentation on running two instances of tomcat on the same Win2000 server and same IP but different ports? Joon Yoo Systems Administrator Ladas Parry LLC 26 West 61st Street New York, NY 10023 tel: (212) 708-1854 fax: (212) 246-8959 This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: documentation on installing two instances of tomcat
You could also check out item (4) in RUNNING.txt under your Tomcat install: Advanced Configuration - Multiple Tomcat 5 Instances. Benjamin J. Armintor Operations Systems Specialist ITS-Systems: Mainframe Group University of Texas - Austin tele: (512) 232-6562 email: [EMAIL PROTECTED] -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 10:03 AM To: Tomcat Users List Subject: RE: documentation on installing two instances of tomcat Hi, Here's some: - Download tomcat .zip - Unpack first installation to a directory of your choice, ports will be 8080 and 8005 by default - Unpack second installation to a different directory of your choice - Edit conf/server.xml of the second installation to something other than 8005 and 8080, say 8006 and 8081. - That's it. Yoav Shapira Millennium Research Informatics -Original Message- From: Yoo, Joon [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 10:55 AM To: ([EMAIL PROTECTED]) Subject: documentation on installing two instances of tomcat Is there any documentation on running two instances of tomcat on the same Win2000 server and same IP but different ports? Joon Yoo Systems Administrator Ladas Parry LLC 26 West 61st Street New York, NY 10023 tel: (212) 708-1854 fax: (212) 246-8959 This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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: documentation to implement the Realm interface aside from javadoc s
Why not downloading the sources from jakarta.apache.org ?? Doyle, Daniel C wrote: I am looking for examples, tutorials, or documentation for implementing the org.apache.catalina.Realm ineterface. Can the Realm implementation point to a servlet? I need to authenticate using a cgi script (don't laugh) on a different web server on a different machine. The cgi will redirect its fail or success response to a URL. Currently, we have the cgi redirect the fail or success response to a JSP. Anyone have design suggestions when implementing a Realm for this architecture. I would look at the code in the CVS repository that currently implement the Realm interface, but I can't get the code as the proxy(which I don't administrate) will not allow CVS traffic(i.e. port not available). Thank you for your time and consideration, Dan Doyle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: documentation to implement the Realm interface aside from javadocs
Howdy, I am looking for examples, tutorials, or documentation for implementing the Examples: http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/s hare/org/apache/catalina/realm/. Also search the list archives for past discussions on this topic. And as evidenced from the link above, you can use ViewCVS over HTTP if your proxy/firewall doesn't like normal CVS (port 2401) traffic. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Documentation
http://jakarta.apache.org/tomcat/ Gaurav Kadyan wrote: Hi All, Could some body tell me where to find documentation for - 1.Realm 2.Filter 3.Valve 4.Container 5.Connector 6.MBean 7.Pipeline 8.LifeCycle 9.Jasper Thanks in advance, Gaurav Kadyan *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. *** For any information on the Quinn Group of Companies please visit :- http://www.quinn-group.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Documentation
Thanks for that Mr. McClanahan, I've already been over those pages with a fine tooth comb and managed to squeeze out what I was after. The problem is just that, I had search for it, and I've looked at it before for other things. There is no direct reference anywhere on it for submitting anything to the documentation, much less how to work with and compile the documentation locally, how to get it out of CVS, nothing. At the very least the how to contribute page needs to be redone to make it easier for everyone who has something to contribute to do it easily. I guess that's where I'll start. Once again I'll say it. Tomcat would really benefit from a documentation project. It's not rocket science, the wheel doesn't have to be invented. There are already good examples of documentation projects to emulate if not down right clone. http://httpd.apache.org/docs-project/ http://apache-server.com/tutorials/ATdocs-project.html thanks again, rls Craig R. McClanahan [EMAIL PROTECTED] 10/02/2002 09:03 AM Please respond to Tomcat Users List To: Tomcat Users List [EMAIL PROTECTED] cc: Subject:RE: Documentation On Tue, 1 Oct 2002, Robert L Sowders wrote: Date: Tue, 1 Oct 2002 22:18:48 -0700 From: Robert L Sowders [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Documentation I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? Sure! From the perspective of the developers, suggested changes to the documentation (or proposed new documents) are treated exactly the same as proposed bug fixes or enhancements to the code itself. Therefore, the best way to submit proposed changes is to create a bug report (or enhancement request) in the bug tracking system: http://nagoya.apache.org/bugzilla/ and then create a patch to the existing documentation files that reflects the change you propose. Details for how to create the diff files for patches is available online starting at: http://jakarta.apache.org/site/getinvolved.html The existing Tomcat documentation can be found in the webapps/tomcat-docs subdirectory of the jakarta-tomcat-4.0 CVS repository. Nearly all of it is in the form of XML files that are post-processed through an XSLT stylesheet to produce the HTML that is ultimately included in the tomcat-docs webapp, as well as posted online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ Changes to the menu bar on the left hand side would be made to the webapps/tomcat-docs/project.html file. General whines about how the documentation sucks will go to /dev/null. Specific patches to add to (or fix) the existing documentation pages are MUCH more likely to be effective :-). rls Craig -- 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]
Re: Documentation
I would also like to help on the docs. Tomcat is a technology that we are betting our software engineering future on right now so I'll be in it for the long haul. I've already written a step-by-step document on how to get Apache, Tomcat, SSL for Apache, JDBC for Oracle, Oracle 9i client, and the Java charting library JFreeChart all installed and working on Red Hat Linux 7.3. Though the document is extremely informal (more like me taking notes during the install), I would not mind turning it into a HOW-TO or something. Just let me know if I can help, Kenny - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 11:03 AM Subject: RE: Documentation On Tue, 1 Oct 2002, Robert L Sowders wrote: Date: Tue, 1 Oct 2002 22:18:48 -0700 From: Robert L Sowders [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Documentation I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? Sure! From the perspective of the developers, suggested changes to the documentation (or proposed new documents) are treated exactly the same as proposed bug fixes or enhancements to the code itself. Therefore, the best way to submit proposed changes is to create a bug report (or enhancement request) in the bug tracking system: http://nagoya.apache.org/bugzilla/ and then create a patch to the existing documentation files that reflects the change you propose. Details for how to create the diff files for patches is available online starting at: http://jakarta.apache.org/site/getinvolved.html The existing Tomcat documentation can be found in the webapps/tomcat-docs subdirectory of the jakarta-tomcat-4.0 CVS repository. Nearly all of it is in the form of XML files that are post-processed through an XSLT stylesheet to produce the HTML that is ultimately included in the tomcat-docs webapp, as well as posted online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ Changes to the menu bar on the left hand side would be made to the webapps/tomcat-docs/project.html file. General whines about how the documentation sucks will go to /dev/null. Specific patches to add to (or fix) the existing documentation pages are MUCH more likely to be effective :-). rls Craig -- 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]
RE: Documentation
We're looking for a Java charting solution. I'd be very interested in seeing a doc on how to use JFreeChart, I've never heard of it before. John -Original Message- From: Kenny G. Dubuisson, Jr. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:08 PM To: Tomcat Users List Subject: Re: Documentation I would also like to help on the docs. Tomcat is a technology that we are betting our software engineering future on right now so I'll be in it for the long haul. I've already written a step-by-step document on how to get Apache, Tomcat, SSL for Apache, JDBC for Oracle, Oracle 9i client, and the Java charting library JFreeChart all installed and working on Red Hat Linux 7.3. Though the document is extremely informal (more like me taking notes during the install), I would not mind turning it into a HOW-TO or something. Just let me know if I can help, Kenny - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 11:03 AM Subject: RE: Documentation On Tue, 1 Oct 2002, Robert L Sowders wrote: Date: Tue, 1 Oct 2002 22:18:48 -0700 From: Robert L Sowders [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Documentation I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? Sure! From the perspective of the developers, suggested changes to the documentation (or proposed new documents) are treated exactly the same as proposed bug fixes or enhancements to the code itself. Therefore, the best way to submit proposed changes is to create a bug report (or enhancement request) in the bug tracking system: http://nagoya.apache.org/bugzilla/ and then create a patch to the existing documentation files that reflects the change you propose. Details for how to create the diff files for patches is available online starting at: http://jakarta.apache.org/site/getinvolved.html The existing Tomcat documentation can be found in the webapps/tomcat-docs subdirectory of the jakarta-tomcat-4.0 CVS repository. Nearly all of it is in the form of XML files that are post-processed through an XSLT stylesheet to produce the HTML that is ultimately included in the tomcat-docs webapp, as well as posted online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ Changes to the menu bar on the left hand side would be made to the webapps/tomcat-docs/project.html file. General whines about how the documentation sucks will go to /dev/null. Specific patches to add to (or fix) the existing documentation pages are MUCH more likely to be effective :-). rls Craig -- 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] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Documentation
Thanks! John -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:03 PM To: Tomcat Users List Subject: RE: Documentation On Tue, 1 Oct 2002, Robert L Sowders wrote: Date: Tue, 1 Oct 2002 22:18:48 -0700 From: Robert L Sowders [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Documentation I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? Sure! From the perspective of the developers, suggested changes to the documentation (or proposed new documents) are treated exactly the same as proposed bug fixes or enhancements to the code itself. Therefore, the best way to submit proposed changes is to create a bug report (or enhancement request) in the bug tracking system: http://nagoya.apache.org/bugzilla/ and then create a patch to the existing documentation files that reflects the change you propose. Details for how to create the diff files for patches is available online starting at: http://jakarta.apache.org/site/getinvolved.html The existing Tomcat documentation can be found in the webapps/tomcat-docs subdirectory of the jakarta-tomcat-4.0 CVS repository. Nearly all of it is in the form of XML files that are post-processed through an XSLT stylesheet to produce the HTML that is ultimately included in the tomcat-docs webapp, as well as posted online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ Changes to the menu bar on the left hand side would be made to the webapps/tomcat-docs/project.html file. General whines about how the documentation sucks will go to /dev/null. Specific patches to add to (or fix) the existing documentation pages are MUCH more likely to be effective :-). rls Craig -- 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]
Re: Documentation
John: I found JFreeChart from a post on this list and it's pretty darn good from what I can tell. Go to http://www.object-refinery.com/jfreechart/index.html. The library is free but the documentation costs $30. I bought the docs and am going through it right now. My main task is getting graphing up and going from data in an Oracle database. I did get graphs up and going on my own using Java's Advanced Imaging library from Sun but JFreeChart has most of the hard work already done. Hope this helps, Kenny - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 11:09 AM Subject: RE: Documentation We're looking for a Java charting solution. I'd be very interested in seeing a doc on how to use JFreeChart, I've never heard of it before. John -Original Message- From: Kenny G. Dubuisson, Jr. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:08 PM To: Tomcat Users List Subject: Re: Documentation I would also like to help on the docs. Tomcat is a technology that we are betting our software engineering future on right now so I'll be in it for the long haul. I've already written a step-by-step document on how to get Apache, Tomcat, SSL for Apache, JDBC for Oracle, Oracle 9i client, and the Java charting library JFreeChart all installed and working on Red Hat Linux 7.3. Though the document is extremely informal (more like me taking notes during the install), I would not mind turning it into a HOW-TO or something. Just let me know if I can help, Kenny - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 11:03 AM Subject: RE: Documentation On Tue, 1 Oct 2002, Robert L Sowders wrote: Date: Tue, 1 Oct 2002 22:18:48 -0700 From: Robert L Sowders [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Documentation I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? Sure! From the perspective of the developers, suggested changes to the documentation (or proposed new documents) are treated exactly the same as proposed bug fixes or enhancements to the code itself. Therefore, the best way to submit proposed changes is to create a bug report (or enhancement request) in the bug tracking system: http://nagoya.apache.org/bugzilla/ and then create a patch to the existing documentation files that reflects the change you propose. Details for how to create the diff files for patches is available online starting at: http://jakarta.apache.org/site/getinvolved.html The existing Tomcat documentation can be found in the webapps/tomcat-docs subdirectory of the jakarta-tomcat-4.0 CVS repository. Nearly all of it is in the form of XML files that are post-processed through an XSLT stylesheet to produce the HTML that is ultimately included in the tomcat-docs webapp, as well as posted online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ Changes to the menu bar on the left hand side would be made to the webapps/tomcat-docs/project.html file. General whines about how the documentation sucks will go to /dev/null. Specific patches to add to (or fix) the existing documentation pages are MUCH more likely to be effective :-). rls Craig -- 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] -- To unsubscribe, e-mail: mailto:[EMAIL
RE: Documentation
On Tue, 1 Oct 2002, Robert L Sowders wrote: Date: Tue, 1 Oct 2002 22:18:48 -0700 From: Robert L Sowders [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Documentation I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? Sure! From the perspective of the developers, suggested changes to the documentation (or proposed new documents) are treated exactly the same as proposed bug fixes or enhancements to the code itself. Therefore, the best way to submit proposed changes is to create a bug report (or enhancement request) in the bug tracking system: http://nagoya.apache.org/bugzilla/ and then create a patch to the existing documentation files that reflects the change you propose. Details for how to create the diff files for patches is available online starting at: http://jakarta.apache.org/site/getinvolved.html The existing Tomcat documentation can be found in the webapps/tomcat-docs subdirectory of the jakarta-tomcat-4.0 CVS repository. Nearly all of it is in the form of XML files that are post-processed through an XSLT stylesheet to produce the HTML that is ultimately included in the tomcat-docs webapp, as well as posted online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ Changes to the menu bar on the left hand side would be made to the webapps/tomcat-docs/project.html file. General whines about how the documentation sucks will go to /dev/null. Specific patches to add to (or fix) the existing documentation pages are MUCH more likely to be effective :-). rls Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Documentation
Thanks! John -Original Message- From: Kenny G. Dubuisson, Jr. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:16 PM To: Tomcat Users List Subject: Re: Documentation John: I found JFreeChart from a post on this list and it's pretty darn good from what I can tell. Go to http://www.object-refinery.com/jfreechart/index.html. The library is free but the documentation costs $30. I bought the docs and am going through it right now. My main task is getting graphing up and going from data in an Oracle database. I did get graphs up and going on my own using Java's Advanced Imaging library from Sun but JFreeChart has most of the hard work already done. Hope this helps, Kenny - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 11:09 AM Subject: RE: Documentation We're looking for a Java charting solution. I'd be very interested in seeing a doc on how to use JFreeChart, I've never heard of it before. John -Original Message- From: Kenny G. Dubuisson, Jr. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:08 PM To: Tomcat Users List Subject: Re: Documentation I would also like to help on the docs. Tomcat is a technology that we are betting our software engineering future on right now so I'll be in it for the long haul. I've already written a step-by-step document on how to get Apache, Tomcat, SSL for Apache, JDBC for Oracle, Oracle 9i client, and the Java charting library JFreeChart all installed and working on Red Hat Linux 7.3. Though the document is extremely informal (more like me taking notes during the install), I would not mind turning it into a HOW-TO or something. Just let me know if I can help, Kenny - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 11:03 AM Subject: RE: Documentation On Tue, 1 Oct 2002, Robert L Sowders wrote: Date: Tue, 1 Oct 2002 22:18:48 -0700 From: Robert L Sowders [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Documentation I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? Sure! From the perspective of the developers, suggested changes to the documentation (or proposed new documents) are treated exactly the same as proposed bug fixes or enhancements to the code itself. Therefore, the best way to submit proposed changes is to create a bug report (or enhancement request) in the bug tracking system: http://nagoya.apache.org/bugzilla/ and then create a patch to the existing documentation files that reflects the change you propose. Details for how to create the diff files for patches is available online starting at: http://jakarta.apache.org/site/getinvolved.html The existing Tomcat documentation can be found in the webapps/tomcat-docs subdirectory of the jakarta-tomcat-4.0 CVS repository. Nearly all of it is in the form of XML files that are post-processed through an XSLT stylesheet to produce the HTML that is ultimately included in the tomcat-docs webapp, as well as posted online: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ Changes to the menu bar on the left hand side would be made to the webapps/tomcat-docs/project.html file. General whines about how the documentation sucks will go to /dev/null. Specific patches to add to (or fix) the existing documentation
RE: Documentation
De: Turner, John [mailto:[EMAIL PROTECTED]] Enviado el: 1 de octubre de 2002 14:12 they should cover. If they did, this list wouldn't get 100-150 messages every night. :-), Please count how many messages of this 100 or 150 are from simply not reading ANY docs... good or bad.. Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Documentation
A pretty high percentage seem to be becuase the docs really are lousy. Wouldn't it be nice to answer 'RTFM' to most of them? When my time frees up on this project I plan on submitting several documentation changes. - Jeff - Original Message - From: Ignacio J. Ortega [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 12:57 PM Subject: RE: Documentation De: Turner, John [mailto:[EMAIL PROTECTED]] Enviado el: 1 de octubre de 2002 14:12 they should cover. If they did, this list wouldn't get 100-150 messages every night. :-), Please count how many messages of this 100 or 150 are from simply not reading ANY docs... good or bad.. Saludos , Ignacio J. Ortega -- 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]
Re: Documentation
I agree with Jeff. The Tomcat documentation reminds me of the old times when I had to compile TeX. A lot of the information for things I have needed to configure in my installation have come from the docs from version 3.3, although I am using 4.0.5. This also makes me worry that some of the things I am using may be deprecated. Cheers, -- Gustavo Vegas. Jeff Wishnie wrote: A pretty high percentage seem to be becuase the docs really are lousy. Wouldn't it be nice to answer 'RTFM' to most of them? When my time frees up on this project I plan on submitting several documentation changes. - Jeff -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Documentation
Hiya Gustavo (and others) I'm going to disagree. The Tomcat docs for the most part are very good. I was able to read them and setup Tomcat to do all the normal things. I can create different contexts, map servlets, create database pools, custom error pages etc. The 4.1.x documentation is updated from the 3.x and 4.0.x documentation and I can't remember it being broken in any real way due to bitrot. Some of the newer features are a little terse, but you have to expect that, then again, there aren't that many How do I configure and create Filters type questions. I haven't tried to use mod_jk yet, but there seems to be a lot of questions about that, but I suspect it's because people haven't read that documentation to start with. Frankly, my rule of mailing lists are that people would rather ask a question because they are too lazy to find the answer themselves. Most of the questions that are asked do exist in the Tomcat documentation, and those that aren't there have generally been answered very clearly by list members. The list is searchable, and Google (www.google.com) is _always_ your friend. This list is certainly one of the most friendly and helpful that I've been on. Sadly that tends to be to it's detriment as people abuse that help. There are definitely areas of the documentation that need work, and potentially others that need cleaning up, but in general they are pretty damn good. Cheers, -- jon Gustavo Vegas wrote: I agree with Jeff. The Tomcat documentation reminds me of the old times when I had to compile TeX. A lot of the information for things I have needed to configure in my installation have come from the docs from version 3.3, although I am using 4.0.5. This also makes me worry that some of the things I am using may be deprecated. Cheers, -- Gustavo Vegas. Jeff Wishnie wrote: A pretty high percentage seem to be becuase the docs really are lousy. Wouldn't it be nice to answer 'RTFM' to most of them? When my time frees up on this project I plan on submitting several documentation changes. - Jeff -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Documentation
-Original Message- From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 6:18 PM I would tend to agree with the above, those writing the code either don't have the inclination or time to write up good documentation. In my mind, these developers should be shot. Or at least confined to a tiny little box for an extended period of time. Or maybe just put in charge of a large data center running their software, and their email and cell phones the only contact info on the 24/7/365 call list. Not to rant, but any developer, open source or not, that writes code but fails to provide good or better documentation at the same time is a poor developer, regardless of their technical skill, and regardless of their commitment or uncompensated participation. I'm no developer, but even I know that documentation is key...I probably spend 60% of my sys-admin time writing recipes and docs for other people to descibe what and how I did the things I did in the other 40%. I think that the argument that the developers don't have time is a cop-out, especially under the Apache style of development and release schedules. There's no pressure to meet release dates in that mode of development, so time is technically unlimited. I would say it's more don't have the inclination because documentation isn't as cool as code and my ego gets more of a boost from writing the latest whiz-bang feature or finding a bug in some other guy's code than it does writing a doc that explains how to perform an installation. Which is a shame. Besides, isn't Java self-documenting? ;) Have you looked at the latest docs for Tomcat 4.1? Much better jk documentation, existing docs updated, and even some new documents at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html I've been all through them, they're pretty much just a rehash of 4.0 docs with a new design template. The new design is pretty, granted, but that's a far cry from where the docs should be. The connector docs are a little better, but in my opinion they don't cover nearly the amount of information they should cover. If they did, this list wouldn't get 100-150 messages every night. That said, I would gladly participate in any documentation project that is started. I could contribute several hours ( 3 time 10 ) each week. Glenn John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Documentation
I'll throw in what I can. Most of my TC docs consist of URLs and hardcopy that I've collected here and there from the web, along with my notes. Put me on your list... If nothing else, it will help me to learn more aobut Tomcat... On Mon, 2002-09-30 at 17:01, Robert L Sowders wrote: Since most of the questions to tomcat-users list concern installation and configuration issues it demonstrates that there is a real need for Tomcat to have a documentation project that it's users can contribute to. Right now most of the documentation consists of the xdocs which are pretty good, but can be so much more. The developers obviously have little time to maintain the present documentation and there is such an apparent need that I wonder why a project for the documentation has not been started. There are many doc-projects out there to emulate. I especially like the one that the apache folks have running, the new xml documentation for Apache 2.0 is probably the best I've seen. I'm sure that many people would be willing to devote some time to organizing and maintaining input from the community into a resource that would benefit everyone. I for one would be willing to contribute, but right now there is nothing an nowhere to submit to. Should the developers of Tomcat initiate a project for the documentation? Or should we? The Apache folks seem to have solved this issue, it remains to be solved for Tomcat. Have a look at some examples of opensouce projects which have solved their documentation problems: http://httpd.apache.org/docs-project/ http://www.freebsd.org/docproj/ http://www.debian.org/doc/ddp http://developer.gnome.org/projects/gdp/ http://www.mulberrytech.com/dsssl/dsssldoc/index.html http://pm-doc.sourceforge.net/ http://zdp.zope.org/ http://www.tldp.org/ rls -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Thad Humphries ...no religious test shall ever be required Web Development Manager as a qualification to any office or public Phone: 540/675-3015, x225trust under the United States. -Article VI -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Documentation
I'm still cleaning up my old document on configuring servletcontextlistener, and servlets, but I'd like to help also. I also think documentation is critical and would like to assist in that effort. peter lin Turner, John wrote: -Original Message- From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 6:18 PM I would tend to agree with the above, those writing the code either don't have the inclination or time to write up good documentation. In my mind, these developers should be shot. Or at least confined to a tiny little box for an extended period of time. Or maybe just put in charge of a large data center running their software, and their email and cell phones the only contact info on the 24/7/365 call list. Not to rant, but any developer, open source or not, that writes code but fails to provide good or better documentation at the same time is a poor developer, regardless of their technical skill, and regardless of their commitment or uncompensated participation. I'm no developer, but even I know that documentation is key...I probably spend 60% of my sys-admin time writing recipes and docs for other people to descibe what and how I did the things I did in the other 40%. I think that the argument that the developers don't have time is a cop-out, especially under the Apache style of development and release schedules. There's no pressure to meet release dates in that mode of development, so time is technically unlimited. I would say it's more don't have the inclination because documentation isn't as cool as code and my ego gets more of a boost from writing the latest whiz-bang feature or finding a bug in some other guy's code than it does writing a doc that explains how to perform an installation. Which is a shame. Besides, isn't Java self-documenting? ;) Have you looked at the latest docs for Tomcat 4.1? Much better jk documentation, existing docs updated, and even some new documents at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html I've been all through them, they're pretty much just a rehash of 4.0 docs with a new design template. The new design is pretty, granted, but that's a far cry from where the docs should be. The connector docs are a little better, but in my opinion they don't cover nearly the amount of information they should cover. If they did, this list wouldn't get 100-150 messages every night. That said, I would gladly participate in any documentation project that is started. I could contribute several hours ( 3 time 10 ) each week. Glenn John -- 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]
RE: Documentation
Hi -1 for shooting developers :-) I can see your point John, but in the real world people are slack and miss bits. Also, as has been pointed out, writing technical notes for technical people is a very different skill to writing a user manual for lay-people. I would rather have the best developers doing the development and the best authors writing the docs. Also a lot of minor patches and fixes are submitted by people other than the core developers - often without updates to the docs (if they are needed). I think the doc project is a good idea. I don't feel I know enough about Tomcat to contribute source (I doubt they would take it :-), but I do feel I have used Tomcat enough to comment on, and maybe even contribute, docs. I am certainly willing to contribute to a project - although I suspect there are people more qualified who have already volunteered. Anthony. -Original Message- From: Turner, John [SMTP:[EMAIL PROTECTED]] Sent: 01 October 2002 13:12 To: 'Tomcat Users List' Subject: RE: Documentation -Original Message- From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 6:18 PM I would tend to agree with the above, those writing the code either don't have the inclination or time to write up good documentation. In my mind, these developers should be shot. Or at least confined to a tiny little box for an extended period of time. Or maybe just put in charge of a large data center running their software, and their email and cell phones the only contact info on the 24/7/365 call list. Not to rant, but any developer, open source or not, that writes code but fails to provide good or better documentation at the same time is a poor developer, regardless of their technical skill, and regardless of their commitment or uncompensated participation. I'm no developer, but even I know that documentation is key...I probably spend 60% of my sys-admin time writing recipes and docs for other people to descibe what and how I did the things I did in the other 40%. I think that the argument that the developers don't have time is a cop-out, especially under the Apache style of development and release schedules. There's no pressure to meet release dates in that mode of development, so time is technically unlimited. I would say it's more don't have the inclination because documentation isn't as cool as code and my ego gets more of a boost from writing the latest whiz-bang feature or finding a bug in some other guy's code than it does writing a doc that explains how to perform an installation. Which is a shame. Besides, isn't Java self-documenting? ;) Have you looked at the latest docs for Tomcat 4.1? Much better jk documentation, existing docs updated, and even some new documents at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html I've been all through them, they're pretty much just a rehash of 4.0 docs with a new design template. The new design is pretty, granted, but that's a far cry from where the docs should be. The connector docs are a little better, but in my opinion they don't cover nearly the amount of information they should cover. If they did, this list wouldn't get 100-150 messages every night. That said, I would gladly participate in any documentation project that is started. I could contribute several hours ( 3 time 10 ) each week. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Documentation
-Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01, 2002 8:12 AM To: 'Tomcat Users List' Subject: RE: Documentation -Original Message- From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 6:18 PM I would tend to agree with the above, those writing the code either don't have the inclination or time to write up good documentation. In my mind, these developers should be shot. Or at least confined to a tiny little box for an extended period of time. Or maybe just put in charge of a large data center running their software, and their email and cell phones the only contact info on the 24/7/365 call list. Not to rant, but any developer, open source or not, that writes code but fails to provide good or better documentation at the same time is a poor developer, regardless of their technical skill, and regardless of their commitment or uncompensated participation. I'm no developer, but even I know that documentation is key...I probably spend 60% of my sys-admin time writing recipes and docs for other people to descibe what and how I did the things I did in the other 40%. There is a big difference between writing policy and administrative doc, and writing product documentation on a product that has a short release cycle. I suppose you could have yearly releases with more polished documentation, but the world is just moving faster than that so lighten up? :-) Bye, Bruce Williams A complex system that works is invariably found to have evolved from a simple system that worked. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[OFF TOPIC] RE: Documentation
-Original Message- From: Bruce Williams [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01, 2002 10:56 AM To: Tomcat Users List Subject: RE: Documentation There is a big difference between writing policy and administrative doc, and writing product documentation on a product that has a short release cycle. I suppose you could have yearly releases with more polished documentation, but the world is just moving faster than that so lighten up? :-) As I pointed out, there is no release cycle in the Apache mode, and there is no release cycle in open source. You release when you feel the product is ready for release, and no sooner. You're also under no threat of liability for providing something sub-standard, so there is no incentive to do so other than laziness or a desire to be the first with the coolest instead of second with the best. No time is an invalid and illogical argument...open source developers have nothing but time. Maybe I'm in the minority, but on the rare occasions I get to write applications, I'm much more satisfied taking an extra day or week and delivering 100% of the package instead of skipping that extra day or week and delivering 70%. It's a very simple matter to include good documentation as a criteria for judging when something should be released. Problem solved. The problem users of open source experience is that a large portion of open source developers typically use it works, there's no docs, but what do they expect for free? as a release criteria. Let's face it...many open source developers get a kick out of saying my app had a certain feature before the app from some-big-company instead of getting a kick out of I delivered the best damn application package anyone has ever seen. some-big-company typically equals Microsoft, IBM, or Oracle. Regarding my own docs, I can assure you they're not policy and administrative docs. Quite the opposite, and in my opinion a recipe for building and deploying a production server, performing a security lock down procdure, or any number of other procedures and processes, is usually much more comprehensive than a document that says this function does X and takes these 3 parameters as arguments. There's a difference between an explanatory document and a step-by-step guide for implementing a solution. I'm not knocking open source developers themselves, only their tendency to avoid providing comprehensive documentation at the same time as providing the application they developed. I honestly can't think of a single logical argument to support not releasing acceptable documentation. What good is spending your own time and effort for free to produce something for people to use if they don't know how to use it and you won't tell them? It makes much more sense to have as big a user-base as you can possibly have, and it gives you a much better return on your time and effort. One of the best ways to increase your user-base is not to decrease (or eliminate) the price, but to help more people understand how to use what you gave them or what is available to them. John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Documentation
I feel your pain John, frustration with poor documentation is always a big sore spot. But let's not line them all up and shoot them just yet, ok. They still need to get Tomcat 5 out the door. ,-) We can only hope that Tomcat-dev (who is reading this list, I hope) will set up some sort of method where people can at least submit changes or updates or something better than what we have now. I've received at least 10 emails off-line and around 5 or so from the list, of people who have things to contribute. We want to help, the question is, can something be done to move to a coordinated effort and who will do it. I submit that it must be controlled and reviewed by the developers themselves. They have access to the resources, we don't, and, they are the authorities on tomcat, they have to be the reviewing authority. I know it will take no small effort to set this up but allot could be cloned from the good example of the Apache Documentation Project. So, are there any developer types lurking out there. We got some documentation help for you, do ya want it? rls Turner, John [EMAIL PROTECTED] 10/01/2002 05:11 AM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Documentation -Original Message- From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 6:18 PM I would tend to agree with the above, those writing the code either don't have the inclination or time to write up good documentation. In my mind, these developers should be shot. Or at least confined to a tiny little box for an extended period of time. Or maybe just put in charge of a large data center running their software, and their email and cell phones the only contact info on the 24/7/365 call list. Not to rant, but any developer, open source or not, that writes code but fails to provide good or better documentation at the same time is a poor developer, regardless of their technical skill, and regardless of their commitment or uncompensated participation. I'm no developer, but even I know that documentation is key...I probably spend 60% of my sys-admin time writing recipes and docs for other people to descibe what and how I did the things I did in the other 40%. I think that the argument that the developers don't have time is a cop-out, especially under the Apache style of development and release schedules. There's no pressure to meet release dates in that mode of development, so time is technically unlimited. I would say it's more don't have the inclination because documentation isn't as cool as code and my ego gets more of a boost from writing the latest whiz-bang feature or finding a bug in some other guy's code than it does writing a doc that explains how to perform an installation. Which is a shame. Besides, isn't Java self-documenting? ;) Have you looked at the latest docs for Tomcat 4.1? Much better jk documentation, existing docs updated, and even some new documents at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html I've been all through them, they're pretty much just a rehash of 4.0 docs with a new design template. The new design is pretty, granted, but that's a far cry from where the docs should be. The connector docs are a little better, but in my opinion they don't cover nearly the amount of information they should cover. If they did, this list wouldn't get 100-150 messages every night. That said, I would gladly participate in any documentation project that is started. I could contribute several hours ( 3 time 10 ) each week. Glenn John -- 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]
RE: Documentation
Great idea. It has been attempted before, in the form of the Hitch-hiker's Guide to Tomcat, http://sourceforge.net/projects/tomcatbook. That project is essentially dead, however. I completely agree with you that something like this would be a wonderful asset to the Tomcat community. ... Mike -Original Message- From: Robert L Sowders [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 5:01 PM To: Tomcat Users List Subject: Documentation Since most of the questions to tomcat-users list concern installation and configuration issues it demonstrates that there is a real need for Tomcat to have a documentation project that it's users can contribute to. Right now most of the documentation consists of the xdocs which are pretty good, but can be so much more. The developers obviously have little time to maintain the present documentation and there is such an apparent need that I wonder why a project for the documentation has not been started. There are many doc-projects out there to emulate. I especially like the one that the apache folks have running, the new xml documentation for Apache 2.0 is probably the best I've seen. I'm sure that many people would be willing to devote some time to organizing and maintaining input from the community into a resource that would benefit everyone. I for one would be willing to contribute, but right now there is nothing an nowhere to submit to. Should the developers of Tomcat initiate a project for the documentation? Or should we? The Apache folks seem to have solved this issue, it remains to be solved for Tomcat. Have a look at some examples of opensouce projects which have solved their documentation problems: http://httpd.apache.org/docs-project/ http://www.freebsd.org/docproj/ http://www.debian.org/doc/ddp http://developer.gnome.org/projects/gdp/ http://www.mulberrytech.com/dsssl/dsssldoc/index.html http://pm-doc.sourceforge.net/ http://zdp.zope.org/ http://www.tldp.org/ rls -- 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]
Re: Documentation
Robert L Sowders wrote: Since most of the questions to tomcat-users list concern installation and configuration issues it demonstrates that there is a real need for Tomcat to have a documentation project that it's users can contribute to. Right now most of the documentation consists of the xdocs which are pretty good, but can be so much more. The developers obviously have little time to maintain the present documentation and there is such an apparent need that I wonder why a project for the documentation has not been started. I would tend to agree with the above, those writing the code either don't have the inclination or time to write up good documentation. Have you looked at the latest docs for Tomcat 4.1? Much better jk documentation, existing docs updated, and even some new documents at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html Regards, Glenn -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Documentation
It would be great to have a website with all the documentation and I would love to help building this website... regards, Alex Robert L Sowders [EMAIL PROTECTED] 30/09/2002 04:01 p.m. Please respond to Tomcat Users List To: Tomcat Users List [EMAIL PROTECTED] cc: Subject:Documentation Since most of the questions to tomcat-users list concern installation and configuration issues it demonstrates that there is a real need for Tomcat to have a documentation project that it's users can contribute to. Right now most of the documentation consists of the xdocs which are pretty good, but can be so much more. The developers obviously have little time to maintain the present documentation and there is such an apparent need that I wonder why a project for the documentation has not been started. There are many doc-projects out there to emulate. I especially like the one that the apache folks have running, the new xml documentation for Apache 2.0 is probably the best I've seen. I'm sure that many people would be willing to devote some time to organizing and maintaining input from the community into a resource that would benefit everyone. I for one would be willing to contribute, but right now there is nothing an nowhere to submit to. Should the developers of Tomcat initiate a project for the documentation? Or should we? The Apache folks seem to have solved this issue, it remains to be solved for Tomcat. Have a look at some examples of opensouce projects which have solved their documentation problems: http://httpd.apache.org/docs-project/ http://www.freebsd.org/docproj/ http://www.debian.org/doc/ddp http://developer.gnome.org/projects/gdp/ http://www.mulberrytech.com/dsssl/dsssldoc/index.html http://pm-doc.sourceforge.net/ http://zdp.zope.org/ http://www.tldp.org/ rls -- 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]
Re: Documentation
Yes, I've seen the new docs, and it looks like they're making an good effort there. The trouble comes with trying to maintain them. By that I mean, when new features are added to Tomcat the docs should reflect them. I don't expect developers to be expert at technical writing, that is another career field all in itself. When documentation becomes stale or is not clear to most you have a problem that requires time to correct. Complicated opensource products require that developers spend more and more time with just developing. Tomcat has reached the plateau where it is just not cost effective for the developers to maintain the documentation any longer. Their time is better spent developing the code, and informing a documentation effort of the new procedures, configuration, or capability. The documentation project then takes care of all the nit picking details required of a good documentation project. The issues of DTD's, CSS, style, third person vs 1st, formal vs informal, and language translation, to name of few, are coordinated by the project to come up with a coherent body of knowledge that mirrors the project itself. Right now if you want to learn the inner workings of Tomcat you have to read the source, pick up clues from various good hearted souls around the net, experiment through trial and error, make buddies with someone who's done it for years, or pay for instructions. For a documentation project to get off the ground the developers have to push for it. They have to be in control of it. Resources for it have to be allocated. (CVS) A single point of authority has to be instituted, an authoritive reference (website) has to initiated, a peer review has to be established. After all this is done then How To's, FAQ's, basic explanations of terms, procedures, and advise, all from one authoritive source will go a long way toward clearing the air and removing the voodoo from Tomcat. One of the big reasons for why commercial outfits tend to go with a commercial container is because of the technical climate surrounding the installation, configuration, and maintenance of Tomcat. If this was simplified or if there was one dependable point of reference that answers could easily be drawn from, it would remove one of the biggest bullets from the gun that decision makers use to shoot down the use of Tomcat. When was the last time that you heard of Apache being disregarded as a viable alternative because it was too hard to install, configure or maintain? I submit that one of the biggest reasons that Apache enjoys the percentage of internet installs that it does is because of it's ease of access to clearly understood documentation. Ok, ok, I know, I'm long winded, so I'll shut up now. I'm really just saying that it's time for it to happen with Tomcat. I'm willing to contribute toward it, I'm sure others will too. rls Glenn Nielsen [EMAIL PROTECTED] 09/30/2002 03:18 PM Please respond to Tomcat Users List To: Tomcat Users List [EMAIL PROTECTED] cc: Subject:Re: Documentation Robert L Sowders wrote: Since most of the questions to tomcat-users list concern installation and configuration issues it demonstrates that there is a real need for Tomcat to have a documentation project that it's users can contribute to. Right now most of the documentation consists of the xdocs which are pretty good, but can be so much more. The developers obviously have little time to maintain the present documentation and there is such an apparent need that I wonder why a project for the documentation has not been started. I would tend to agree with the above, those writing the code either don't have the inclination or time to write up good documentation. Have you looked at the latest docs for Tomcat 4.1? Much better jk documentation, existing docs updated, and even some new documents at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html Regards, Glenn -- 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]
Re: documentation on mod_jk
Ukiah, there are several places where you could find information. The most detailed one could be found here: http://atlassw1.phy.bnl.gov/jakarta-tomcat/mod_jk-howto.html If there still are questions go to http://www.galatea.com/flashguides/index Cheers and good luck, Nick Ukiah Smith wrote: I am looking for a how-to or other documentation on configuring mod_jk. I have installed it, and it serves the basic dynamic pages from tomcat. I want information that explains how to configure so that I can create my own custom configs instead of copying the examples without really understanding them. thanks //Ukiah Smith -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Nikolas A. Rathert Fraunhofer Institute for Computer Graphics e-Learning Knowledge Management Fraunhoferstrasse 5 D-64283 Darmstadt Germany Fon +49 6151 155 552 Fax +49 6151 155 569 email: [EMAIL PROTECTED] www: http://www.igd.fhg.de -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: documentation location
Google is your friend! http://java.sun.com/j2ee/sdk_1.2.1/techdocs/api/javax/mail/package-summary.h tml EG - Original Message - From: Øyvind Vestavik [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, April 22, 2002 1:36 PM Subject: documentation location Where can i find javadoc for this package?? package javax.mail.* Øyvind Øyvind Vestavik Øvre Møllenberggt 44b 7014 Trondheim [EMAIL PROTECTED] 41422911 -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Documentation - Class Loader Info
On Thu, 10 Jan 2002 [EMAIL PROTECTED] wrote: Date: Thu, 10 Jan 2002 16:36:12 -0500 From: [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Documentation - Class Loader Info All, My apologies if this email is not appropriate for this list. While going through the documentation for configuring Tomcat 4.0.1, I came across a couple of discrepancies: In the document for Class Loader Info, I noticed that under Class Loader Definitions - System section mentions the CLASSPATH environment variable is initialized using two jars, namely $CATALINA_HOME/lib/bootstrap.jar and $JAVA_HOME/lib/tools.jar. On the standard installation of Tomcat 4.0.1, the bootstrap.jar file is present in the $CATALINA_HOME/bin directory rather than the $CATALINA_HOME/lib directory. I presume this was probably an oversight. If this was not the case then perhaps do we need to copy the file from the $CATALINA_HOME/bin directory to the $CATALINA_HOME/lib directory. Nope ... that is typo in the docs. The files are in the right place. The other is also in the same document in the section discussing the order in which the class or resource loader looks for the various classes. $CATALINA_HOME/common/classes or $CATALINA_HOME/common do not contain any jar files, but the jars are present in $CATALINA_HOME/common/lib. I was wondering if we need to copy all the files from the $CATALINA_HOME/common/lib directory to either the $CATALINA_HOME/common/classes directory or to the $CATALINA_HOME/common directory. That's another typo -- that entry should really be: $CATALINA_HOME/common/lib/*.jar I found this out when I was trying to compile the HelloWorld servlet example and kept on getting the class not found error again and again. Any pointers on this will be helpful. Thanks in advance, Samarth I will check in the documentation fixes today. Thanks! Craig -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Documentation for VM crash under Linux
On Thu, 2001-12-06 at 04:55, Renato wrote: I saw people telling about documentation of VM crashes under Linux and that there are some workarounds on the release notes. It doesn't seem to be there. Could anyone point me out where I could find this docs ? The release notes are available from the J2SE download page. For J2SE 1.3.1_01, it's at http://java.sun.com/j2se/1.3/relnotes.html. The Vertual Machine section mentions several problems with various versions of Linux. -- Weiqi Gao [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Documentation for VM crash under Linux
Thanks !! What about IBM's ? Any issues we shold be aware of ? On Thu, 2001-12-06 at 04:55, Renato wrote: I saw people telling about documentation of VM crashes under Linux and that there are some workarounds on the release notes. It doesn't seem to be there. Could anyone point me out where I could find this docs ? The release notes are available from the J2SE download page. For J2SE 1.3.1_01, it's at http://java.sun.com/j2se/1.3/relnotes.html. The Vertual Machine section mentions several problems with various versions of Linux. -- Weiqi Gao [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Documentation for Tomcat 4.0
Steven- I am running Tomcat 3.2.1, so I don't know if this will be true for Tomcat 4.x. I would expect it to be true, though. The Tomcat user guide describes server.xml, web.xml and user.xml. Find it in TOMCAT_HOME\doc\uguide\tomcat_ug.html where TOMCAT_HOME is the Tomcat top-level installation directory. Example: E:\Jakarta\jakarta-tomcat-3.2.1\doc\uguide\tomcat_ug.html I don't think it's accessible via links from the Tomcat server home page. You have to explicitly enter the URL or open the file from your browser through the File/Open browser menu item. Barry Draper IBM Informix Oakland, CA -Original Message- From: Steven Elliott [mailto:[EMAIL PROTECTED]] Sent: Friday, July 27, 2001 8:20 AM To: [EMAIL PROTECTED] Subject: Documentation for Tomcat 4.0 I have gone over the server.xml. I have gone over the web.xml. I have gone over the user.xml. I have been through both the Developer and Developing Applications With Tomcat documentation. Unless I've missed some documentation somewhere I've gone over all of it at least once if not at least twice. Nowhere did I come across the Alias / XML tag for the server.xml but I did find it mentioned in the email archives as I was searching for Virtual Host information. Please if someone could point me in the direction of where I might find the documentation for the server, user and web xml files (Tomcat v.4) I would really, really appreciate it. TIA Steven Elliott [EMAIL PROTECTED] Systems Integrator Interactive Tecnologia, Lda. LisbonPortugal tel: +351 21 440 8090 fax: +351 21 441 7242 --
Re: Documentation for Tomcat 4.0
On Fri, 27 Jul 2001, Steven Elliott wrote: I have gone over the server.xml. I have gone over the web.xml. I have gone over the user.xml. I have been through both the Developer and Developing Applications With Tomcat documentation. Unless I've missed some documentation somewhere I've gone over all of it at least once if not at least twice. Nowhere did I come across the Alias / XML tag for the server.xml but I did find it mentioned in the email archives as I was searching for Virtual Host information. The server.xml docs are not 100% complete yet, but this one is in fact mentioned. Start up Tomcat, and browse to: http://localhost:8080/docs/config/index.html and select the Host element in the navigation menu. Down near the bottom (in the Special Features section), you will find documentation on Host Name Aliases, which covers the nested Alias element. (From the Tomcat default home page, follow the General Tomcat User Documentation link, followed by Server Configuration). Please if someone could point me in the direction of where I might find the documentation for the server, user and web xml files (Tomcat v.4) I would really, really appreciate it. For server.xml stuff, see the link above. For web.xml, that is defined in the Servlet Specification, which you can download from: http://java.sun.com/products/servlet/download.html Tomcat 4 conforms to the most recent Proposed Final Draft of the Servlet 2.3 and JSP 1.2 specifications. TIA Steven Elliott [EMAIL PROTECTED] Systems Integrator Interactive Tecnologia, Lda. LisbonPortugal tel: +351 21 440 8090 fax: +351 21 441 7242 -- Craig McClanahan
RE: documentation about cvs
http://www.cvshome.org/docs/index.html Jason -Original Message- From: Pedro Henrique Ponchio [mailto:[EMAIL PROTECTED]] Sent: Friday, March 09, 2001 3:46 PM To: [EMAIL PROTECTED] Subject: documentation about cvs Please, anyone can send me an url about CVS documentation? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: documentation about cvs
http://www.cvshome.org/docs/manual/index.html - Original Message - From: "Pedro Henrique Ponchio" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 09, 2001 9:45 PM Subject: documentation about cvs Please, anyone can send me an url about CVS documentation? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Documentation for web.xml, server.xml updated
I've re-uploaded the javadocs. FTP burped last time, I guess it missed a bunch of files. That has been corrected. I'm adding examples now. Mike Very, very nice!!! That's a lot of good stuff in one place. One note however, in clicking around the 3.2.x internal Javadocs, I got a number of 404 not found errors. -- Rob --On Thursday, March 08, 2001 02:29:16 PM -0800 Mike Slinn [EMAIL PROTECTED] wrote: I've put more time into the Tomcat documentation at http://www.mslinn.com/sites/tomcat Any comments and suggestions would be appreciated. Mike Slinn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Documentation for web.xml, server.xml updated
Looks like a great job. Adding some examples would make it perfect. -Original Message- From: Mike Slinn [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 08, 2001 5:29 PM To: [EMAIL PROTECTED] Subject: Documentation for web.xml, server.xml updated I've put more time into the Tomcat documentation at http://www.mslinn.com/sites/tomcat Any comments and suggestions would be appreciated. Mike Slinn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Documentation for web.xml, server.xml updated
Very, very nice!!! That's a lot of good stuff in one place. One note however, in clicking around the 3.2.x internal Javadocs, I got a number of 404 not found errors. -- Rob --On Thursday, March 08, 2001 02:29:16 PM -0800 Mike Slinn [EMAIL PROTECTED] wrote: I've put more time into the Tomcat documentation at http://www.mslinn.com/sites/tomcat Any comments and suggestions would be appreciated. Mike Slinn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ _ _ _ __ _ _ _ _ /\_\_\_\_\/\_\ /\_\_\_\_\_\ /\/_/_/_/_/ /\/_/ \/_/_/_/_/_/ QUIDQUID LATINE DICTUM SIT, /\/_/__\/_/ __/\/_//\/_/ PROFUNDUM VIDITUR /\/_/_/_/_/ /\_\ /\/_//\/_/ /\/_/ \/_/ /\/_/_/\/_//\/_/ (Whatever is said in Latin \/_/ \/_/ \/_/_/_/_/ \/_/ appears profound) Rob Tanner McMinnville, Oregon [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: documentation for jk_nt_service.exe
Hi Betty, Link to jk_nt_service.exe documentation: http://jakarta.apache.org/cvsweb/index.cgi/jakarta-tomcat/src/doc/NT-Service-howto.html and select the hyperlinkRevision 1.2/ (as text) -- Susmitha Vuyyuru Developermailto:[EMAIL PROTECTED] 1.650.314.0936 Portal Wave, Inc.The Fastest Track to Integrated e-Businesswww.portalwave.com -Original Message-From: Betty Chang [mailto:[EMAIL PROTECTED]]Sent: Friday, December 08, 2000 10:52 PMTo: [EMAIL PROTECTED]Subject: documentation for jk_nt_service.exe Hi -- where in the apache.org site is the documentation for how to use jk_nt_service.exe? Thanks
Re: documentation for jk_nt_service.exe
http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/NT-Service-howto.html try this site
Re: documentation for jk_nt_service.exe
http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/NT-Service-howto.html It's a bit difficult to find the documentation for Tomcat on apache.org... At 22:52 00/12/08 -0800, you wrote: Hi -- where in the apache.org site is the documentation for how to use jk_nt_service.exe? Thanks
