You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "A B (JIRA)" <ji...@apache.org> on 2007/04/10 23:55:32 UTC
[jira] Created: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488209 ]
A B commented on DERBY-2538:
----------------------------
Thank you for picking this up, Kim, and for posting the changes so quickly.
I've read over the changes as you have them and they look good. I have to admit, though, that something about the phrase "use the JDBC 4 API" has me hesitating...
In a way I guess I'm just applying Bryan's earlier question to this particular phrase, namely:
How do I know if my application "uses the JDBC 4 API"? Does this mean that the application explicitly calls methods which are only available in the JDBC 4 API? If so, then does that mean that an application which runs on the Java SE 6 platform but which does not use any JDBC4-specific APIs is *not* "using the JDBC 4 API"? Technically I think such an application still has the option of using either DataSource variant...
In some ways I wonder if it would be clearer to just focus on the jdk/platform. I.e.:
----
Applications that run on the J2SE 1.4 or 1.5 platform must use the first variant. Applications that run on the Java SE 6 platform can use either of the two variants. However, the DataSource methods specific to the JDBC 4 API are available only from the second variant (the one whose class name ends with "40").
If an application is running on the Java SE 6 platform, all connection objects returned from the DataSource will be JDBC 4 connection objects, regardless of which DataSource variant is in use.
----
This then goes back to Bryan's other question: is this [really] just a question of what JDK I'm using? If so, then would the above snippet be good enough?
On a different note, I glanced at the "Network Server and Administration Guide" and I noticed there are two pages about DataSources there, as well. Once we figure out what it is we want to say, these two pages should probably be updated accordingly:
http://db.apache.org/derby/docs/dev/adminguide/cadminnsdatasources.html
http://db.apache.org/derby/docs/dev/adminguide/cadminappsxawthdriver.html
In fact, I think it might be good to change the first of these so that it more closely matches the content of http://db.apache.org/derby/docs/dev/devguide/rdevresman79556.html, with the appropriate datasource name changes...
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488120 ]
Kim Haase commented on DERBY-2538:
----------------------------------
I can implement this -- I think I can make sure the wording is appropriate.
> 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
> Assigned To: Kim Haase
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489198 ]
A B commented on DERBY-2538:
----------------------------
The version 4 changes look good to me. +1 to commit pending resolution of DERBY-2488.
Thank you for addressing this so quickly, Kim!
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488701 ]
A B commented on DERBY-2538:
----------------------------
> After reading DERBY-2488, I am wondering if the description of the client DataSource interfaces
> in the Admin Guide (both cadminnsdatasources.dita and cadminappsxawthdriver.dita) ought to
> have some version of the following text in rdevresman79556.dita:
+1, I think this is a good idea.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Updated: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2538:
-----------------------------
Attachment: DERBY-2538-3.zip
DERBY-2538-3.diff
Whoops! Sorry about that. Here is a clean patch, I hope. Thanks for catching that.
After reading DERBY-2488, I am wondering if the description of the client DataSource interfaces in the Admin Guide (both cadminnsdatasources.dita and cadminappsxawthdriver.dita) ought to have some version of the following text in rdevresman79556.dita:
"If an application is running on the Java SE 6 platform, all connection objects
returned from the DataSource will be JDBC 4 connection objects,
regardless of which DataSource variant is in use."
That is, assuming DERBY-2488 continues in the same direction it seems to be heading. I agree it makes sense to wait on completing this issue till that issue is resolved.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Updated: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2538:
-----------------------------
Attachment: rdevresman79556.html
cdevresman89722.html
DERBY-2538.diff
I've attached the patch DERBY-2538.diff, which modifies these files:
M src/devguide/rdevresman79556.dita
M src/devguide/cdevresman89722.dita
It's probably best to be as clear as possible about the relationship between JDK and JDBC versions. So I've been explicit. I think this text works for 10.3; it refers to JDK 1.4, 1.5, and 6, and removes the reference to JDBC 2 (which applied when we supported JDK 1.3, but not now).
I don't find "environment" used in reference to either JDBC or the JDK, so I used other terms that are correct. Hope this works.
I moved the javadoc reference to the end of rdevresman79556.dita as suggested. I also took the liberty of making a few more formatting and language fixes,
mainly for consistency within the topics.
Please let me know if further changes are needed. I've attached the HTML output.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488438 ]
Kim Haase commented on DERBY-2538:
----------------------------------
Thanks, Army! I think you are right -- it really is just a matter of which JDK you are using. The JDBC version information is not essential, and removing it definitely keeps things simpler.
I'll work on a new patch that uses your suggested language. And I'll also work on updating those Admin Guide topics along the same lines. If any more suggestions come along, I'll adapt accordingly.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487947 ]
Bryan Pendleton commented on DERBY-2538:
----------------------------------------
> Applications that are running in a JDBC 2 or JDBC 3 environment ...
How do I know what environment my application is running in? It seems like
maybe we need a paragraph in the docs somewhere which describes what
it means for an application to be running in a certain JDBC environment. For
example, is this just a question of what JDK I'm using? Did we invent the
terminology "JDBC environment" or is this part of the JDBC specification?
> 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.
[jira] Resolved: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
A B resolved DERBY-2538.
------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
Thank you for the commit, Laura.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Updated: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2538:
-----------------------------
Attachment: DERBY-2538-4.zip
DERBY-2538-4.diff
Attaching DERBY-2538-4.diff and DERBY-2538-4.zip, adding the language about the Connection objects to the Admin Guide files. I changed the wording slightly because those files don't use the term "variant."
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Closed: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
A B closed DERBY-2538.
----------------------
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491099 ]
Laura Stewart commented on DERBY-2538:
--------------------------------------
Yes, I have the source set up. I'll go ahead and commit this doc patch.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Updated: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2538:
-----------------------------
Attachment: DERBY-2538-2.zip
DERBY-2538-2.diff
Attaching DERBY-2538-2.diff and DERBY-2538-2.zip, which incorporate Army's suggested changes (I hope).
M src/devguide/rdevresman79556.dita
M src/devguide/cdevresman89722.dita
M src/adminguide/cadminappsxawthdriver.dita
M src/adminguide/cadminnsdatasources.dita
Please let me know if any additional changes would be helpful.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491101 ]
Laura Stewart commented on DERBY-2538:
--------------------------------------
Committed revision 531651.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Assigned: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-2538:
--------------------------------
Assignee: Kim Haase
> 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
> Assigned To: Kim Haase
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491097 ]
A B commented on DERBY-2538:
----------------------------
The patch for DERBY-2488 has been committed and that issue is now resolved. So if any committers out there have the documentation source set up (I don't; maybe Laura?), I think DERBY-2538-4.diff can be committed...
Thanks again, Kim.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Updated: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2538:
-----------------------------
Derby Info: [Patch Available]
Just realized you reviewed this, Army, without my having marked it Patch Available -- that was above and beyond the call of duty!
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488517 ]
A B commented on DERBY-2538:
----------------------------
Thanks Kim, these look good to me.
I think there's one blip in the cadminnsdatasources.html file: the following line appears after the ellipses, but I don't think it's supposed to be there...
Be42,in43
Other than that I think the updates are good to go. Of course, DERBY-2488 is still open and pending review, so it might be a good idea to wait until all discussion for that issue is closed before updating the documentation (just in case something changes between now and then).
It's great that you've been willing and able to address this need so quickly--thanks a ton for your help! If DERBY-2488 gets resolved as it is, then I vote +1 to commit these doc changes. But it might be good to wait for that issue's resolution before going ahead with the commit...
Does that sound okay?
Thanks again.
> 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
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> 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.
[jira] Commented: (DERBY-2538) Update documentation to describe the
expected behavior when a JDBC 4 app creates a JDBC 3 datasource.
Posted by "A B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487954 ]
A B commented on DERBY-2538:
----------------------------
> is this just a question of what JDK I'm using?
Great question. Maybe JDK would in fact be clearer here. I went with "JDBC" because the connection objects we are talking about implement (or don't) the JDBC 4 interface methods. Use of "jdk 1.6" seemed slightly less appropriate to me because it seems like it could theoretically be possible to have more than one jdk that correlates to JDBC 4 (ex. jdk 1.4 and 1.5 both correlate to JDBC 3).
But I am notorious for messing up the JDK/JVM/JDBC terminology, so you're probably right. I'll wait to see if anyone out there offers better wording.
> Did we invent the terminology "JDBC environment" or is this part of the JDBC specification?
Another good question. I just typed what came to me...maybe that's not a good way of phrasing it. I did notice that in one of his comment Dan wrote:
"In a JDK 1.4/1.5 environment the applications must use the old ones (e.g. EmbeddedConnectionPoolDataSource)"
So perhaps that's the wording that should go here...
> 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.