db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1271) Release documentation for JDBC4 release
Date Tue, 09 May 2006 22:21:05 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1271?page=all ]

Rick Hillegas updated DERBY-1271:
---------------------------------

    Description: 
We can't check in any of this work until we understand how our release trains line up. However,
the JDBC4-bearing release will need the following documentation:

1) Changes to the user guides. These need to be understood. We can analyze the scope of these
changes without checking anything in yet.

2) Summary page which explains what pieces of JDBC4 we tackled and what we passed over.

3) Verbiage for the Release Notes.

USER GUIDES

Admin Guide


  Part One...How to start an embedded server from an application

    For JDBC4, we can omit the Class.forName() line because
    of Driver autoloading.

  Part One...Embedded server example

    For JDBC4, we can omit the Class.forName() line because
    of Driver autoloading.

  Part One...Network client driver examples

    For JDBC4, we can omit the Class.forName() line because
    of Driver autoloading.

  Part One...Accessing the Network Server by using a DataSource

    For JDBC4, we have different DataSources: ClientDateSource40
    and ClientConnectionPoolDataSource40.

  Part One...Using the Derby ij tool with the Network Server

    In case the DRIVER command ends up being needed pre-JDBC4,
	we should note that you don't need it under JDBC4 because
	of Driver autoloading.

  Part One...The NsSample sample program

    Change NsSample to demonstrate driver autoloading under JDBC4.

  Part One...Overview of the SimpleNetworkServerSample program

    Change SimpleNetworkServerSample to demonstrate driver autoloading under JDBC4.

  Part One...Connecting a client to the Network Server with the SimpleNetworkClientSample
program

    Change SimpleNetworkClientSample to demonstrate driver autoloading under JDBC4.



  was:
We can't check in any of this work until we understand how our release trains line up. However,
the JDBC4-bearing release will need the following documentation:

1) Changes to the user guides. These need to be understood. We can analyze the scope of these
changes without checking anything in yet.

2) Summary page which explains what pieces of JDBC4 we tackled and what we passed over.

3) Verbiage for the Release Notes.



Added description of changes needed for the Admin Guide.

> Release documentation for JDBC4 release
> ---------------------------------------
>
>          Key: DERBY-1271
>          URL: http://issues.apache.org/jira/browse/DERBY-1271
>      Project: Derby
>         Type: Improvement

>   Components: Documentation, JDBC
>     Versions: 10.2.0.0
>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>      Fix For: 10.2.0.0

>
> We can't check in any of this work until we understand how our release trains line up.
However, the JDBC4-bearing release will need the following documentation:
> 1) Changes to the user guides. These need to be understood. We can analyze the scope
of these changes without checking anything in yet.
> 2) Summary page which explains what pieces of JDBC4 we tackled and what we passed over.
> 3) Verbiage for the Release Notes.
> USER GUIDES
> Admin Guide
>   Part One...How to start an embedded server from an application
>     For JDBC4, we can omit the Class.forName() line because
>     of Driver autoloading.
>   Part One...Embedded server example
>     For JDBC4, we can omit the Class.forName() line because
>     of Driver autoloading.
>   Part One...Network client driver examples
>     For JDBC4, we can omit the Class.forName() line because
>     of Driver autoloading.
>   Part One...Accessing the Network Server by using a DataSource
>     For JDBC4, we have different DataSources: ClientDateSource40
>     and ClientConnectionPoolDataSource40.
>   Part One...Using the Derby ij tool with the Network Server
>     In case the DRIVER command ends up being needed pre-JDBC4,
> 	we should note that you don't need it under JDBC4 because
> 	of Driver autoloading.
>   Part One...The NsSample sample program
>     Change NsSample to demonstrate driver autoloading under JDBC4.
>   Part One...Overview of the SimpleNetworkServerSample program
>     Change SimpleNetworkServerSample to demonstrate driver autoloading under JDBC4.
>   Part One...Connecting a client to the Network Server with the SimpleNetworkClientSample
program
>     Change SimpleNetworkClientSample to demonstrate driver autoloading under JDBC4.

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