In this section
The Code Style site has evolved by gradual refinement and accumulation of features and content. This review is part of a fully backdated site log and archive that sheds light on when, why and how particular features were implemented.
This log is sometimes updated several times per week, sometimes with a long overdue backlog of items. Many log entries refer to the Code Style Java package that delivers the servlet services and utilities used to manage this site.
Subscribe to the news feed for this log: 
Reverse chronology
FAQ backlog, 30th April 2006
Added a backlog of 14 new answers in multiple sections, including Javascript, Web fonts, Java programming, Java language and servlet containers, as follows:
JSP tags & libraries
Java API
Java compiler
Java interface design
Java programming
Java servlet "how to"
Java servlet API
-
What's the difference between
doGet()anddoPost()? -
What's the difference between
GenericServletandHttpServlet?
Javascript
Tomcat configuration
Web fonts
Also moved right-hand local navigation panels to vertically align with the left-hand Options navigation.
Exception handling for empty user agent, 22nd April 2006
Returned to the log file parse errors found on 14th April, where the user agent field is the empty string, and added an exception handler to the CombinedLogParser class to deal with it properly. The catch NoSuchElementException block inserts [None].
Stack trace for log parse errors, 14th April 2006
Added a stack trace output to the RssAgentLogger class to find the cause of unexpected exceptions parsing Metacentric service logs to update the Feed reader reference. The trace revealed a NoSuchElementException on the StringTokenizer nextToken method used to extract the log field data. Eventually isolated the case where the user agent entry is the empty string. Manually deleted the problem lines as a short term fix.
Previously on Code Style
These backdated pages record detailed changes to the Code Style Web site since July 2000, when development first got underway. Some pages may refer to documents or features that have since changed or are no longer part of the site, but the archive is checked to ensure there are no dead links.
Site log, origins to present
For a summary overview, see the annotated site log contents.
