RE: Tomcat Documentation Thoughts
That's useful thanks Ben :) Allistair. > -Original Message- > From: Ben Souther [mailto:[EMAIL PROTECTED] > Sent: 24 November 2004 14:55 > To: Tomcat Users List > Subject: RE: Tomcat Documentation Thoughts > > > >Let's get a page detailing a step by step how to write and contribute > > >documentation and then let's get Tomcat's docs up to > scratch by really > > >considering the areas that come up time and again in the lists and > > making > > >the Tomcat documentation deserving of its functional reputation. > > There's the tech guide at http://www.apache.org/dev/contributors.html. > > The xdoc format is self-explanatory. Then you submit your > patches in > > Bugzilla and we take care of building them. > > > > There is this also. > http://jakarta.apache.org/site/jakarta-site2.html > > -Ben > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- QAS Ltd. Developers of QuickAddress Software http://www.qas.com";>www.qas.com Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Documentation Thoughts
with a maximum file size of 500KB and up to 10 backups. DEBUG level is specified which will result in the most verbose output from Tomcat. The above can generate in excess of 5MB of logging with bundled web applications and Struts web applications. You can of course choose to be more picky about which packages to include in the logging as with the JDK Logging. For example try substituting the last line of the above configuration with one of these: log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost]=DEBUG, R log4j.logger.org.apache.catalina.core=DEBUG, R log4j.logger.org.apache.catalina.session=DEBUG, R The usefulness of what you will find from internal Tomcat logging is debatable for web applications. Unless a problem with Tomcat itself exists, it is probably not required. It is much more common and recommended for web application themselves to be configured with a logging setup. In the case of JDK Logging, you could setup package loggers to collect logging from your own applications, e.g com.mycomp.myapp.level=DEBUG. In the case of log4j, a custom log4j.properties file would be placed into your web application's WEB-INF/classes folder and log4j-1.2.8.jar into WEB-INF/lib and the log4j.properties file would setup a set of (normally) file appenders to collect the logging, again with package level setup, e.g log4j.logger.org.mycomp.myapp=DEBUG, APPENDER_TO_USE. > -Original Message- > From: Wouter De Vaal [mailto:[EMAIL PROTECTED] > Sent: 24 November 2004 14:54 > To: Tomcat Users List > Subject: Re: Tomcat Documentation Thoughts > > > On Wed, 24 Nov 2004 09:44:00 -0500, Shapira, Yoav > <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > >But you know, I submitted a logging page doc patch over a > week ago and > > it's > > >still not there, and since then there have been many posts > asking about > > >this problem. I don't find that encouraging. > > > Is this about my problem that I posted earlier today (tomcat 5.5.4 and > log4j)? About the > ...[host].[/] problem? > If so, could you please post your fix on this to me or this list? > > Regards, > Wouter de Vaal > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- QAS Ltd. Developers of QuickAddress Software http://www.qas.com";>www.qas.com Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Documentation Thoughts
On Wed, 24 Nov 2004 09:44:00 -0500, Shapira, Yoav <[EMAIL PROTECTED]> wrote: > > Hi, > > >But you know, I submitted a logging page doc patch over a week ago and > it's > >still not there, and since then there have been many posts asking about > >this problem. I don't find that encouraging. > Is this about my problem that I posted earlier today (tomcat 5.5.4 and log4j)? About the ...[host].[/] problem? If so, could you please post your fix on this to me or this list? Regards, Wouter de Vaal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Documentation Thoughts
>Let's get a page detailing a step by step how to write and contribute > >documentation and then let's get Tomcat's docs up to scratch by really > >considering the areas that come up time and again in the lists and > making > >the Tomcat documentation deserving of its functional reputation. There's the tech guide at http://www.apache.org/dev/contributors.html. > The xdoc format is self-explanatory. Then you submit your patches in > Bugzilla and we take care of building them. > There is this also. http://jakarta.apache.org/site/jakarta-site2.html -Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Documentation Thoughts
Hey :) > >But you know, I submitted a logging page doc patch over a > week ago and it's > >still not there, and since then there have been many posts > asking about > >this problem. I don't find that encouraging. > > As I responded, your patch has been committed, and it will be > available > in the next release. If you want something sooner or more dynamic, > that's why we have a wiki. Yes but the logging applies to the current release too and people are asking about it. Is the web page build quite an intensive process? I don't want to labour on the point, I just think documentation should be a priority, not a per-Tomcat-build thing. > >Also, there is very little documentation on how to even document! > Tomcat > >developers make a lot of suggestions to people to "go write > a document > >then" but never cite a definitive reference for how one > would do that. > >There's a small page on how to build Tomcat but that's your > lot (please > >correct me if I am wrong!). So that's a page I think could > be helpful. > > There's the tech guide at http://www.apache.org/dev/contributors.html. > The xdoc format is self-explanatory. Then you submit your patches in > Bugzilla and we take care of building them. Well it's something but it doesn't apply to Tomcat directly. The docs are wrapped up in jakarta-catalina in webapps folder. I had to download nearly everything to find that out. he jakarta-site2 is misleading ... (this site it says). My point again is this scattering of information rather than a definitive Tomcat resource. People don't want to scout the web piecing together information on how to get a product up and going imo. > I'm glad you have the time to help, and I look forward to seeing your > contributions. :) ok. > Happy thanksgiving ;) Yes of course, I forgot it's thanksgiving for you guys!! Enjoy :) Allistair. --- QAS Ltd. Developers of QuickAddress Software http://www.qas.com";>www.qas.com Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Documentation Thoughts
Hi, >But you know, I submitted a logging page doc patch over a week ago and it's >still not there, and since then there have been many posts asking about >this problem. I don't find that encouraging. As I responded, your patch has been committed, and it will be available in the next release. If you want something sooner or more dynamic, that's why we have a wiki. >Also, there is very little documentation on how to even document! Tomcat >developers make a lot of suggestions to people to "go write a document >then" but never cite a definitive reference for how one would do that. >There's a small page on how to build Tomcat but that's your lot (please >correct me if I am wrong!). So that's a page I think could be helpful. There's the tech guide at http://www.apache.org/dev/contributors.html. The xdoc format is self-explanatory. Then you submit your patches in Bugzilla and we take care of building them. >Let's get a page detailing a step by step how to write and contribute >documentation and then let's get Tomcat's docs up to scratch by really >considering the areas that come up time and again in the lists and making >the Tomcat documentation deserving of its functional reputation. I've added a section to the wiki page at http://wiki.apache.org/jakarta-tomcat/HowTo. I'm glad you have the time to help, and I look forward to seeing your contributions. Happy thanksgiving ;) 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]
Tomcat Documentation Thoughts
Citing "Thank you for sharing. It IS useful information. Now if newbies would only search the archives before posting the same questions, we'd be all set! ;)" Mmm, of course it would be great, but mailing lists are not in reality the place people look for documentation for world-class software products. They are not particularly usable, and much of it is conversation without solution, a lot of time can be wasted. The prevalence of Tomcat is obvious and synonymous in my view with J2EE web application development. But on the documentation front, BEA, IBM and the like out-do Tomcat easily. This will be a factor in Tomcat's ultimate success. Our .net boys have just completed their first ever project in J2EE/Tomcat/Struts/Hibernate and they had real problems and time loss scouting mailing lists and the web for documentation on configuration with IIS with respect to SSL and Virtual Hosting - 2 prevalent technologies used everywhere. Same goes for the other technologies (you know they are used to wizards lol) but there is some truth in it. I understand that with an open-source product this is never going to be the case and it relies on contributors to the project. For my part, I would like to help where I can with Tomcat's documentation and as you know I started that. I am going to think about the areas I think improvement can be made and make those suggestions. But you know, I submitted a logging page doc patch over a week ago and it's still not there, and since then there have been many posts asking about this problem. I don't find that encouraging. Also, there is very little documentation on how to even document! Tomcat developers make a lot of suggestions to people to "go write a document then" but never cite a definitive reference for how one would do that. There's a small page on how to build Tomcat but that's your lot (please correct me if I am wrong!). So that's a page I think could be helpful. Turns out you need an understanding of CVS, making a patch, the XDOC format. I had to scout all the Apache website to form a full view of how to do this. And how do you even preview your changes? Probably by having to grab Apache Forrest or something. Let's get a page detailing a step by step how to write and contribute documentation and then let's get Tomcat's docs up to scratch by really considering the areas that come up time and again in the lists and making the Tomcat documentation deserving of its functional reputation. Allistair. > -Original Message- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 24 November 2004 14:05 > To: Tomcat Users List > Subject: RE: SuSE 9.2 and Tomcat... > > > > Hi, > Thank you for sharing. It IS useful information. Now if > newbies would > only search the archives before posting the same questions, > we'd be all > set! ;) > > Yoav Shapira http://www.yoavshapira.com > > > >-Original Message- > >From: Quinton Delpeche [mailto:[EMAIL PROTECTED] > >Sent: Wednesday, November 24, 2004 2:28 AM > >To: [EMAIL PROTECTED] > >Subject: SuSE 9.2 and Tomcat... > > > >Hi Again, > > > >Well after pulling my hair out and getting very frustrated I have > finally > >fixed and documented everything that needs to be done in order to get > >Tomcat > >5 working on SuSE 9.2. > > > >This seems a little strange since I am using the version of > Tomcat that > >comes > >with SuSE 9.2, but I won't say anymore on the matter. > > > >There are basically two important permission things that need to be > done. > > > >1). The files admin.xml and manager.xml > >in /etc/tomcat5/base/Catalina/localhost/ need to be given > write access > to > >the > >tomcat user. > > > >There new profile should look like this: > >-rw-rw-r-- 1 root tomcat 862 Oct 5 03:20 admin.xml > >-rw-rw-r-- 1 root tomcat 428 Oct 5 03:20 manager.xml > > > >This fix removes the previous error regarding the admin and manager > >applications that I posted earlier. > > > >2). The tomcat user needs to be given access to /var/run in order to > create > >the relevant PID file. > > > >Because my server is behind a firewall and I change the ROOT and user > >password > >on the server regularly, I changed the /var/run permissions so that > >everyone > >could read and write from and to this directory. > > > >The new profile should look like this: > >drwxrwxrwx 15 root root 1032 Nov 24 09:11 run > > > >This fix solves various issues regarding the admin and manager > applications > >as > >well as the start.log error. > > > >Thats it. I don't know if this information will be useful to anyone, > but I > >thought I would share it with you all anyway. > > > >Regards > >Q > >-- > >Quinton Delpeche > >Internal Systems Developer > >Softline VIP > > > >Telephone: +27 12 420 7000 > >Direct:+27 12 420 7007 > >Facsimile: +27 12 420 7344 > > > >http://www.vippayroll.co.za/ > > > > A doctor, an architect, and a computer scientist were arguing > >about whose profession was the oldest.
