db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3983) User Guide documentation on the limitations of small-device support is stale
Date Wed, 24 Dec 2008 14:22:44 GMT

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

Rick Hillegas commented on DERBY-3983:

Thanks for picking this up, Kim.

Some of the existing bullets refer to limitations in the JSR 169 api itself (1 and 7), some
refer to limitations in Derby's implementation (4, 5, 6). I am not sure about bullet 3 but
it seems to me to be a Derby limitation that you can't configure an EmbeddedSimpleDataSource
to hand back the current connection. I confess that I don't understand bullet 2: the CONTAINS
SQL, READS SQL, and MODIFIES SQL DATA language comes from the SQL Standard and is not part
of the JDBC api; I don't know what the reference to "parameters" means.

As far as Xalan is concerned,  you might reproduce what is said about the XML Data Type in
the Reference Guide. Thanks.

> User Guide documentation on the limitations of small-device support is stale
> ----------------------------------------------------------------------------
>                 Key: DERBY-3983
>                 URL: https://issues.apache.org/jira/browse/DERBY-3983
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
> The limitations of Derby's feature set on small devices is sketched in the Reference
Guide in a section titled "JDBC Package for Connected Device Configuration/Foundation Profile
(JSR169)". This section should be expanded to include other unsupported features identified
in DERBY-3966:
> 1) Lack of XML datatype (can be remedied if the small device platform can be supplemented
with some extra, freely available jar files)
> 2) Non-blocking io
> 3) Java EE resource manager support, including distributed transactions
> 4) Principal-based security
> 5) LDAP-based authentication
> 6) SSL/TLS encryption
> 7) Replication

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

View raw message