[jira] Commented: (DERBY-2538) Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.

["A B (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487932 ] 

A B commented on DERBY-2538:
----------------------------

Suggested changes:

1) http://db.apache.org/derby/docs/dev/devguide/rdevresman79556.html

  Delete the paragraph that begins with "Each of these DataSources...". Replace it with:

  ----

  Derby provides two variants of each DataSource interface defined by J2EE,
  as shown below.  Applications that are running in a JDBC 2 or JDBC 3
  environment <bold>must<bold> use the first variant.  Applications that are
  running in a JDBC 4 environment can use either of the two variants.  However,
  the DataSource methods specific to JDBC 4 are only available from the second
  variant (the one whose class name ends with "40").

  Note that in a JDBC 4.0 environment all connection objects returned from the
  DataSource will be JDBC 4 connection objects, regardless of which DataSource
  variant is in use.

  The Derby implementation classes for the J2EE DataSource interfaces are as
  follow:

  ----

Also, might be good to move the first sentence on the page ("See the javadoc for each class for more information.") to the end of the page.  Just seems more natural there.

2) http://db.apache.org/derby/docs/dev/devguide/cdevresman89722.html

Replace:

  // Note that if your application runs on JDK 1.6 or higher, you
  // will use the JDBC4 variants of these classes:

with:

  // Note that if your application is running in a JDBC 4 environment and
  // you would like to call DataSource methods specific to JDBC 4 (ex.
  // "isWrapperFor(...)" then you should use the JDBC 4 variants of these
  // classes:

These are of course first drafts; feedback/improvements/suggestions are welcome.

> Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2538
>                 URL: https://issues.apache.org/jira/browse/DERBY-2538
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions: 10.2.2.0, 10.3.0.0
>            Reporter: A B
>            Priority: Minor
>
> Based on discussion from DERBY-2488, pages in the Developer's Guide should be improved to describe what happens if a JDBC 4 application uses an "old" (JDBC 3) datasource.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.