Rearranged to support test as well as interactive modes

QueryException interactive example

Test passes with query

Simple write test is OK

Initial attempt to provide sample for trycatchredo

platform and ide cluster increased cluster numbers and we need to change the download locations

Taking code snippets from tests

Shortening long line

Initial version of sample to explain 'code injection'

Shortening long lines

Adding day.end.bridges.DigestImpl code snippet

Typo and bigger code snippet

Files shall be referenced to their actual version. Only that makes the links always valid

two code snippets were named the same

Showing use of "plain" factories

it is builder.creation

Tests for magical bag - e.g. overuse of lookup

Adding builder pattern

Fixing broken code section

Renaming the AServerInfo class to ServerConnector and spliting it into three separate classes.

Renaming arguments

Showing API for AServerInfo

Too long line

Petr Nejedl? discovered that surrounding variable definition with { } does not guarantee it to be removed from stack

Moving into real packages

Rewriting the initialization to be more meaningful for clueless reader that does not need to understand every detail

extracting the accessor initialization outside of the API block of the Item class

Wrong English in method name

ljnelson noted at 'http://weblogs.java.net/blog/jst/archive/2008/10/the_better_comp.html' that it is enough to make the variable final and the problem goes away. True, final helps, however the same code without final works as well. This very likely means that the compiler puts the variable into the topmost block where it is guaranteed to be fully initialized. That is why we need a hint warn about declaration of non-fully initialized variables.

Too long lines