Has someone got any ideas of how we are gonna gather all the information? I
have some things that come to mind, which can be forgotten tomorrow ;-).
Maby by using the faq that was around in the jserv erra ;) and add entries
there? Or is someone already gonna be a mail repository for this?
Maby I can setup a mailinglist on my server for this, until we get things
really running. Still fighting with the mailinglist a bit, but if the idea
is welcomed, I'll make it a "spare time" top priority.
Mvgr,
Martin van den Bemt
> -----Original Message-----
> From: Thomas Bezdicek [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 04, 2001 4:11 PM
> To: [EMAIL PROTECTED]
> Subject: AW: PROPOSAL: Tomcat docs
>
>
> > More refinements... if i didn't quote it, I agree with it =) BTW, what
> > does "AW" in a subject line mean? I see it all the time...
> AW = Antwort which is pretty the same like RE=reply in english,
> except that
> it is in german :) Its done by outlock.
>
> > 0) Introduction to the TC4 container
> > ADD > - Requirements (JDK versions, extra libs?, etc.)
> agree
>
> > 1) "User's Guide" (or "Administrator's")
> > > - Tomcat and different JDK Versions
> > Moved this up to (0)
> agree
>
> > > 2) "<web app development w/Tomcat>" Can't think of a title =)
> > > ^
> > > Tomcat Webdeveloper Guide
> >
> > I think we do need to separate out the fact that there are a
> > group of people
> > who will developing/embedding/extending Tomcat, and a group of
> people that
> > will be developing web applications for Tomcat. As a web
> > developer, I don't care a lot of about Tomcat's internals ;)
> Ok, but I think it is better to split the pure administrator stuff
> from what ever kind of developer stuff.
> developers who want to extend/embedd tomcat will be much more interessted
> in the api-docs and specs. normal webdevelopers arent interessted in that.
>
> 2) Tomcat Development Guide
> - Web developers
> - extending/embedding Tomcat
>
> > 3) "Tomcat Upgrade Guide"
> >
> > I think this would equate to a lot of feature mapping from one
> > container to
> > another. The Admin's guide should suffice. REALLY all you
> need to do is
> > drop a .WAR file in and change the port to get the container running
> > standalone.
> ask someone who ported from jserv to tomcat :)) just the zone handling
> (which was a real crap in jserv) ... and for those upgrading from servlet
> api 2.2 to 2.3 there might also be some tiny changes which might result
> in a major problem ...
> and even the what is a ".war" file would be much help for beginners.
>
> > > 4) "Appendix"
> >
> > Suggest that we move this all up into (0). I'd like people to
> know these
> > things asap =) With the history of doc reading, I dunno anyone
> would make
> > it this far!
> hmm, I do. (like me)
>
>
> tom
>
>
