db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2361) Documentation should give examples for using the different security mechanisms
Date Tue, 20 Mar 2007 18:46:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase updated DERBY-2361:

    Attachment: DERBY-2361-3.diff

Actually, I had better revise the patch to reflect the addition of the new file as well as
the recent changes to the refderby.ditamap file.

svn stat src/ref
A      src/ref/rrefattribsecmech.dita
M      src/ref/refderby.ditamap

svn stat src/adminguide
M      src/adminguide/cadminapps811631.dita
M      src/adminguide/cadminapps49914.dita

It would be helpful to get feedback from John Embretsen and/or Andrew McIntyre.

> Documentation should give examples for using the different security mechanisms
> ------------------------------------------------------------------------------
>                 Key: DERBY-2361
>                 URL: https://issues.apache.org/jira/browse/DERBY-2361
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Andrew McIntyre
>         Assigned To: Kim Haase
>         Attachments: DERBY-2361-2.diff, DERBY-2361-2.zip, DERBY-2361-3.diff, DERBY-2361.diff,
DERBY-2361.zip, rrefattribsecmech.dita, rrefattribsecmech.dita-2
> The Derby Server and Administration guide talks about the different security mechanisms,
but does not give examples of how these can be used via connection URLs, it only mentions
the client DataSource field names. 
> http://db.apache.org/derby/docs/10.2/adminguide/cadminapps49914.html
> The documentation should give examples of how to use the different security mechanisms
via connection URLs, and perhaps an example of how the client field names would be used programmatically.

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

View raw message