db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Kartha (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-382) Doc Review: Derby Reference Manual
Date Sun, 26 Jun 2005 03:03:00 GMT
    [ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314496 ] 

Rajesh Kartha commented on DERBY-382:
-------------------------------------

Following are some of the thoughts/changes/suggestions for the Reference  Guide:

1) Reference Guide -> Setting attributes for the database connection URL -> encryptionProvider=providerName

	If this attribute is not specified, the default encryption provider is com.sun.crypto.provider.SunJCE.
(?)
	(Need to confirm this - what if ibm jdks are used, will it still be SunJCE ?)


2) Reference Guide -> Derby API ->  JDBC implementation classes -> JDBC driver

Currently there is mention of only the embedded driver, the new Derby Network client driver
also needs to be added here.

This is the JDBC driver for the Derby Network Server:
• org.apache.derby.jdbc.ClientDriver

Used to connect to the Derby Network Server in client-server mode. See the Derby Developer's
Guide.

3) Reference Guide -> Derby API ->  JDBC implementation classes -> Data Source Classes

Currently there is mention of only the embedded driver, the new Derby Network client driver
also needs to be added here.

• org.apache.derby.jdbc.ClientDataSource
• org.apache.derby.jdbc.ClientConnectionPoolDataSource
• org.apache.derby.jdbc.ClientXADataSource 


> Doc Review: Derby Reference Manual
> ----------------------------------
>
>          Key: DERBY-382
>          URL: http://issues.apache.org/jira/browse/DERBY-382
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>  Environment: all
>     Reporter: Jeff Levitt
>     Priority: Minor
>      Fix For: 10.1.1.0

>
> This issue tracks comments for the Derby Reference Manual. The deadline for posting comments
is Tuesday, June 28, noon Pacific time.
> Some guidelines to follow when posting comments to this issue are:
> - Try to make clear and concise comments about what you want changed whenever possible.
 Provide concrete comments that say "Please change <original> to <modified>" instead
of generic comments like "This section needs to be rewritten."
> - If you're reviewing the HTML Files copy, include the URL for the page in the review
comment. Obtain the URL like this:
>     * highlight the topic in the left frame
>     * right click
>     * choose "Properties"
>     * copy and paste the address in the pop up box.
> - If you're reviewing the PDF copy, in the review comment:
>     * Include the page number for the PDF, and indicate whether the number is the PDF
sheet number or the printed page number.
>     * Include the title of the section that the problem occurs in. If it's in a subsection,
try to include the hierarchy of titles.
> - Please don't review the HTML Book copy -- it'll be time consuming to match up that
copy with the underlying DITA source.

-- 
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


Mime
View raw message