Kim Haase created DERBY-6478:
--------------------------------

             Summary: Fix language about supported DataSources for Compact 
Profiles
                 Key: DERBY-6478
                 URL: https://issues.apache.org/jira/browse/DERBY-6478
             Project: Derby
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 10.11.0.0
            Reporter: Kim Haase
            Assignee: Kim Haase
            Priority: Minor


Knut Anders Hatlen pointed out the following in his review of a patch for 
DERBY-6236:

"One little inaccuracy in the changed text (existing problem, not introduced by 
the patch): It seems to imply that only the basic data sources work on Compact 
Profile 3. That is not the case. The ordinary data sources are supported on 
CP3. Only CP2 lacks the necessary classes (javax.naming.*) and need the basic 
data sources. (The basic data sources do work on CP3, though, so it's not a 
problem if applications choose to use them if they don't need the extra 
functionality of the ordinary data sources.)"

This means that numerous topics in the Admin Guide, Reference Manual, and 
Developer's Guide probably need some fixes. For example, the topic "JDBC 
support for Java SE 8 Compact Profiles" in the Reference Manual should probably 
add something like the following at the end of the topic:

"Users of Compact Profile 3 on the Java SE 8 platform can use either these 
DataSource classes or the Datasource classes for the full Java SE platform." 

As another example, the topic "Network client security" in the Admin Guide 
should probably be changed to something like this:

"Derby provides two ClientDataSource implementations. Use the 
org.apache.derby.jdbc.ClientDataSource class on all supported Java SE versions 
except Java SE 8 Compact Profiles 1 and 2. On Java SE 8 Compact Profile 2, use 
the org.apache.derby.jdbc.BasicClientDataSource40 class."

Please let me know if these tweaks need further tweaking -- in the meantime I 
will start work on implementing them. Thanks.



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

Reply via email to