[ http://issues.apache.org/jira/browse/DERBY-1948?page=comments#action_12441509 ] Kim Haase commented on DERBY-1948: ----------------------------------
In addition to the corrections listed above (thanks to Micky for catching them!), I'm adding the following technical corrections. twwdactivity1.dita: - change output 10.2.1.0 to 10.2.1.6 - Build is 452058 twwdactivity2.dita: - command output is not "Server is ready to accept connections on port 1527." but Apache Derby Network Server - 10.2.1.6 - (452058) started and ready to accept connections on port 1527 at 2006-09-22 00:08:30.049 GMT I edited the timestamps to correlate approximately with those in the output examples. - shutdown command also different: Apache Derby Network Server - 10.2.1.6 - (452058) shutdown at 2006-09-22 00:16:30.049 GMT - both messages later in file as well rwwdactivity3.dita: - changed "java program" to "Java program" (2nd paragraph) - changed "SQLException method" to "SQLExceptionPrint method" near end - changed "JAVA" to "Java" at end twwdactivity4.dita: - This activity leaves the Network Server running. Added a step to shut it down. Will attach a diffs file that includes all these changes. > 10.2 'Working with Derby' manual errors. > ---------------------------------------- > > Key: DERBY-1948 > URL: http://issues.apache.org/jira/browse/DERBY-1948 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.2.1.6 > Environment: Under Fedora core 5 > Reporter: Micky Connor > Assigned To: Kim Haase > Priority: Trivial > > Going through the 10.2 'Working with Derby' manual I think I > have found several file path errors: > --Under Activity 1, the given path is > $DERBY_HOME/demo/toursdb/*.sql > but it should be > $DERBY_HOME/demo/programs/toursdb/*.sql > --Similary, under Activity 3, in section 1, the given path is > $DERBY_HOME/demo/workingwithderby/* > but it should be > $DERBY_HOME/demo/programs/workingwithderby/* > --Finally under Activity 4, section 3, the CLASSPATH given for Windows refers > to 'derbyclient.jar', but the UNIX version gives 'derby.jar'. The > necessary driver only exists in 'derbyclient.jar'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
