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