Mark, On 12/12/12 3:13 PM, Mark Thomas wrote: > On 12/12/2012 19:59, Christopher Schultz wrote: >> Mark, > >> On 12/12/12 4:42 AM, ma...@apache.org wrote: >>> Author: markt Date: Wed Dec 12 09:32:51 2012 New Revision: >>> 1420586 >>> >>> URL: http://svn.apache.org/viewvc?rev=1420586&view=rev Log: >>> Update website t.0.x docs to 7.0.34 > >> Did we ever decide that the API Javadoc for javax.servlet was >> copywritten and therefore could not be included in Tomcat sources? >> We discussed it a while back. > > The current javax.servlet.* Javadoc is correctly licensed under the > ALv2. There are no issues with the current source.
Okay. > For the classes where there are gaps, the Javadoc *may not* be copied > from the reference implementation (or any other source unless the > source has an appropriate license and the necessary entries are made > in LICENSE and NOTICE). It must be written independently from > knowledge of the specification. > > You'll notice that it is mainly Servlet 3.0 and 3.1 changes where > there are gaps. Yeah, this was really where my question was aimed: the new stuff for 3.0. > Practically, this is a little tricky since you have to read the RI > Javadoc to get a full understanding of the specification. I tend to > read up on an area that I am working on (Javadoc, spec, Tomcat's > implementation), do the work and then write the Javadoc. Okay. My go-to reference for the servlet API are those pages hosted by ASF under the Tomcat umbrella. So, it's a PITA when stuff isn't documented. I can't seem to find any online servlet API documentation from Oracle -- you have to download it and view it locally. Is our only option to read the RI javadocs, forget them, then try to document from scratch? -chris
signature.asc
Description: OpenPGP digital signature
