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

Rick Hillegas commented on DERBY-3983:
--------------------------------------

Thanks, Kim. This is a big improvement. It looks good to me.

I have given some more thought to your question about the distinction between 
JSR169's limitations and Derby's limitations. I don't think the distinction is 
interesting to the user.  I think that the user merely wants to come away from 
our user guides understanding:

1) What features always work on small devices (presumably anything not 
mentioned on this webpage)

2) What features might work on small devices if you included the correct 
libraries (e.g., the XML datatype

3) What features never work on small devices (all of the other stuff listed on 
the page). If we wanted to invest some effort in refining this list, we might 
be able to identify some optional packages which the user could ship with their 
small platform and which would move some of the items in (3) up into (2). That 
could be a follow-on JIRA.

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: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-3983.diff, rrefjdbcjsr169.html
>
>
> 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.

Reply via email to