[WWD] Chap 3 and 4 submitted for review - Derby dev invitation

[Stanley Bradbury <St...@gmail.com>]

For those of you who did not notice this in the flurry of JIRA messages 
that go by.  Please participate in the review if you have time.  I am 
particularly interested in feedback for the development community on the 
code example used for Activity 3.  Below is a copy of my post to Derby 
User - it includes additional information.
    -   -   -

I've submitted Activities 2 and 3 (Chapters 3 and 4) of the Work With Derby [WWD] 
document for feedback.
This latest revision of Working With Derby has been posted to Jira.  It 
can be downloaded using:

http://issues.apache.org/jira/secure/attachment/12324531/WWDpdfNjava0323.zip

This contains the newly completed chapters 3 and 4.  Please focus first 
on the initial review of these chapters.  The PDF file and related JAVA 
code are contained in the file:  WWDpdfNjava0323.zip

The revisions of chapters 1 and 2 are also included.  This is their 
second review since restructuring the scope of the project and contain 
modifications based on information from the first review.  Please review 
and comment on these revisions as time allows.

Format Change Note:
Chapters 1 - 4 contain a structural change to the Basic Activity Format 
proposed.  Feedback received  (i.e. 'I keep jumping back and forth') 
indicated that the Basic Activity Format (Item 1 on the 'Feedback 
Requested' list) was not the best way to present this material.  The new 
format has  the descriptive text interspersed with the command and 
output examples.  The new activity format is step description followed 
by example then the next-step description followed by example, etc.

Some other changes that have been made besides correcting typOs and 
syntax errors:

A short section describing each activity was added to Ch 1.

The toursDB.sql script with the anticipated path has replaced 
'something.sql' as the script that is loaded in Activity 1.

References to 10.1 were updated to 10.2

The introduction is now warmer and more inviting.  If you can think of 
other eloquent words I might add, please let me know (I do not stand out 
when it comes to being eloquent).

The introduction of  shutdown=true was moved to Activity 3.

Responses to commands (aka output) is italicized to help differentiate 
user input from output in the examples - for long command sequences 
(e.g. running WwdEmbedded) the input is in bold.