db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6236) Remove references to old JVMs (pre-Java 6) from the user guides
Date Fri, 07 Feb 2014 13:56:19 GMT

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

Knut Anders Hatlen commented on DERBY-6236:
-------------------------------------------

{quote}
So maybe it makes sense to say something like "Local JMX management and monitoring are enabled
by default on platforms that support JMX. (Java SE 8 Compact Profile 2, for example, does
not support JMX.)" in the enabling/disabling topic.
{quote}

Sounds good!

{quote}
I'm not sure it's necessary to say anything at all in the jconsole topic. Hmm, do the compact
profiles support jconsole even?
{quote}

Since jconsole talks to Derby via JMX, and JMX is not available on Compact Profile 2, I don't
think you could connect to a Derby instance running on Compact Profile 2. I agree that it's
sufficient to mention the restriction in the enabling/disabling JMX topic.

{quote}
In the Reference Manual, it seems to me that not only "Features supported on all JDBC 4 releases"
but also "Features supported on JDBC 4.1 and above" can be merged into the main JDBC topics,
since JDBC 4.1 applies to JDK 6 and above.
{quote}

Actually, I think the "Features supported on JDBC 4.1 and above" is wrong about this. It says
"JDBC 4.1 features are present only in a JDK 6 or higher environment." It should say 7. Java
6 had JDBC 4.0. Although... Derby's JDBC 4.0 drivers include all the JDBC 4.1 functionality,
so it's true that you can access the features on Java 6 as well, with some creative casting.
But not through the JDBC interfaces.

{quote}
By the way, does the information in the Developer's Guide section "Working with Derby SQLExceptions
in an application" also apply to working with the refined subtypes of SQLException? I am guessing
it does.
{quote}

I couldn't find anything that wasn't valid for the refined subtypes. So I think you are correct.

> Remove references to old JVMs (pre-Java 6) from the user guides
> ---------------------------------------------------------------
>
>                 Key: DERBY-6236
>                 URL: https://issues.apache.org/jira/browse/DERBY-6236
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>
> DERBY-6213 removed support for Java 5 and CDC. We need to scour references to these platforms
from our user documentation. This includes scouring references to JDBC 3.0 and JSR 169. Changes
include the following:
> -------- Admin Guide -------------
> o "Differences in JDBC 3.0 methods": The section should be renamed to "Differences in
JDBC methods" and references to JDBC 3.0 should be removed from its text.
> -------- Developer's Guide -------------
> o "Derby and Java Virtual Machines (JVMs)": the lowest supported JVM level should be
changed from 5 to 6.
> -------- Getting Started Guide -------------
> o "System requirements": the lowest supported JVM level should be changed from 5 to 6.
> o"Verifying the Derby system configuration": bullet 1, references to Java version 5 should
be changed to 6.
> o "Self-study tutorial for users new to Derby": references to JDK version 5 should be
changed to 6.
> -------- Reference Guide -------------
> o "JDBC reference": Change "JDBC 3.0 and 4.0 APIs" -> "JDBC API"
> o "java.sql.Driver interface": This section gives instructions on how to load the JDBC
driver if you are running on an old (pre-Java 6) JVM. The section is almost vacuous now. It
can be collapsed to the following summary:
> "The class that loads Derby's local JDBC driver is the class org.apache.derby.jdbc.EmbeddedDriver.
The class that loads Derby's network client driver is the class org.apache.derby.jdbc.ClientDriver."
> o "JDBC Package for Connected Device Configuration/Foundation Profile (JSR 169)": Remove
this section.
> o "Features supported on all JDBC 4 releases": This section should be removed and its
material should be merged into the preceding sections.
> o "DataSource classes": The following changes should be made.
> "Embedded environment, for applications running on JDK 5 or higher and using JDBC 3 and
JDBC 4.0 methods:" -> "Embedded environment, for applications running on Java 6 or higher:"
> Remove the following paragraph and the list of *40 DataSources which it introduces:
> "Embedded environment, for applications running on JDK 6 or higher and using methods
specific to JDBC 4.1 or JDBC 4.2:"
> "Client-server environment, for applications running on JDK 5 or higher and using JDBC
3 and JDBC 4.0 methods:" -> "Client-server environment, for applications running on Java
6 or higher:"
> Remove the following paragraph and the list of *40 DataSources which it introduces:
> "Client-server environment, for applications running on JDK 6 or higher and using methods
specific to JDBC 4.1 or JDBC 4.2:"
> -------- Tools Guide -------------
> o "Environment setup and the Derby tools": The minimum Java level is 6, not 5.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message