Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=llwBg6e3NwkmFtH8Wxihve9Ku16letA9JzOWf3R27QmM5AGjEoYVDBeItp8j4EfB0QDYu1yojIHOkuBMwvqQbb+H513i9XaX5QDQo77LSQdKDttFKqy35hIK5y0H4x8ysETo9B8OHaOBBaVOT/VIoMq9F6052ip3zjk40s5gTPM=
  ;
Message-ID: <20060324001418.72547.qmail@web81303.mail.mud.yahoo.com>
Date: Thu, 23 Mar 2006 16:14:18 -0800 (PST)
From: Susan Cline <home4slc@pacbell.net>
Subject: Re: [WWD] Chap 3 and 4  submitted for review
To: Derby Discussion <derby-user@db.apache.org>
In-Reply-To: <44232A00.6060402@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

--- Stanley Bradbury <Stan.Bradbury@gmail.com> wrote:

> I've submitted Chapters 1 and 2 of the Work With Derby [WWD] document 
> for feedback.
> The 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

[ snip ]

I unzipped the file and looked at the PDF, but I do not see a chapter 4.  I see an Intro,
Activity 1, Activity 2 and Activity 3.  Do chapters 3 and 4 correspond to Activity 2 and Activity
3?

I like the Activity 3 example.  One suggestion would be is to check the command line parameter
to make sure it is not over 32 characters.  I "made a wish" for something that was over
32 characters and got a stack trace that was not too user friendly.

It might be nice for new derby users (and if they happened to be new to Java too) to
get a usage message instead of a stack trace if they made this same error.

Thanks,

Susan