This page is for reviewing the 10.2 ''Derby Developers Guide''.
This page just has initial Section Summary and Sub Section Details set up. The Reference Manual has a complete review setup.
Section Summary
Please list the sections you intend to review in the summary table below:
Section Name |
Reviewers |
Status |
Sunitha |
review done for first half of book,posted mail to the derby dev with subject 'Dev guide: sections - upgrades to controlling derby application behavior.'http://www.nabble.com/Dev-guide%3A-sections---upgrades-to-controlling-derby-application-behavior.-p6110021.html |
|
Sunitha |
review done |
|
Sunitha |
review done |
|
Sunitha |
review done |
|
Sunitha |
review done |
|
Sunitha |
review done |
|
Sunitha |
review done |
|
Deepa |
review done |
|
Deepa |
review done |
|
Deepa |
review done |
|
Deepa |
review done |
|
Deepa |
review done |
|
Deepa |
review done |
Sub Section Details
As you spot issues please add specific comments to the tables below, paying attention to the guidelines. For very extensive comments, please post to derby-dev or Jira instead, then include the URL in the Comment field.
Upgrades:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
|
|
Sunitha |
Fixed (Laura) |
JDBC applications and Derby basics:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
|
|
Sunitha |
Fixed (Laura) |
After installing:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
|
|
Sunitha |
Fixed (Laura) |
Derby embedded basics:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
|
|
Sunitha |
Fixed (Laura) |
Deploying Derby applications:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
|
|
Sunitha |
Fixed (Laura) |
Derby server-side programming:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
|
|
Sunitha |
Fixed (Laura) |
Controlling Derby application behavior:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
|
|
Sunitha |
Fixed (Laura) |
Using Derby as a J2EE resource manager:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
Getting a DataSource |
http://db.apache.org/derby/docs/dev/devguide/cdevresman89722.html |
Deepa |
"XADataSource.getXAConection() method" and "XADataSource.getXAConnection().getConnection() method" should be changed to more general "getConnection method of data source object." |
Fixed (Laura) |
Derby and Security:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
Built-in Derby users |
http://db.apache.org/derby/docs/dev/devguide/cdevcsecure21547.html |
Deepa |
To keep the terminology consistent, "These user names are case-sensitive for user authorization" should be changed to "These user names are case-sensitive for user authentication". |
Fixed (Laura) |
Notes on the Derby security features |
http://db.apache.org/derby/docs/dev/devguide/cdevcsecure10983.html |
Deepa |
This statement should be removed "Because Derby does not support traditional grant and revoke features, the security model has some basic limitations." as grant/revoke is supported now. I think the following two lines "For both embedded and client/server systems, it assumes that users are trusted. You must trust your full-access users not to perform undesirable actions." can also be removed. |
Fixed (Laura) |
JNDI-specific properties for external directory services |
http://db.apache.org/derby/docs/dev/devguide/cdevcsecure864242.html |
Deepa |
"Java Naming and Direction" should be changed to "Java Naming and Directory". |
Fixed (Laura) |
Example of setting a user-defined class |
http://db.apache.org/derby/docs/dev/devguide/rdevexudclass.html |
Deepa |
The interface specified in the following line "A very simple example of a class that implements the org.apache.derby.authentication interface." must be "org.apache.derby.authentication.UserAuthenticator interface". |
Fixed (Laura) |
Example of setting a user-defined class |
http://db.apache.org/derby/docs/dev/devguide/rdevexudclass.html |
Deepa |
In the first comment in the code example, "derby.connection.specificAuthentication" property is not the right name. It must be changed to "derby.authentication.provider". |
Fixed (Laura) |
List of user-authentication properties |
http://db.apache.org/derby/docs/dev/devguide/rdevcsecure557.html |
Deepa |
Formatting and case of property names is not consistent. |
Fixed (Laura) |
User authorizations |
http://db.apache.org/derby/docs/dev/devguide/cdevcsecure36595.html |
Deepa |
Sub-section titled "Changes to connection authorization settings" can be changed to "Changes to user authorization settings" as it applies to both SQL and connection authorization. |
Didn't change this since the section is about connection authorization (Laura) |
Encrypting an existing unencrypted database |
http://db.apache.org/derby/docs/dev/devguide/tdevcsecureunencrypteddb.html |
Deepa |
minor typos. Must be "encrypted" instead of "encryped". "For encrypting an existing unencrypted database:" instead of "To encrypting an existing unencrypted database:" |
Fixed (Laura) |
Developing tools and using Derby with an IDE:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
SQL Tips:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
Localizing Derby:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |
Derby and standards:
Sub Section |
HTML Url or PDF Page |
Reviewer |
Comment |
Resolution |