[
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-4.zip
DERBY-2361-4.diff
Thanks, Laura, that's a good suggestion. See what you think of this latest
patch (DERBY-2361-4.diff, DERBY-2361-4.zip), which I hope includes all your
comments. (I gave the two files matching numbers; hope that doesn't confuse
anyone.)
The other changes to the security mechanisms topic included the bold font you
suggested; mentioning explicitly that the values are numeric; and changing the
description from "Specifies a non-default security mechanism" to just
"Specifies a security mechanism", since we are including the defaults.
> 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: 10.2.2.0
> Reporter: Andrew McIntyre
> Assigned To: Kim Haase
> Attachments: DERBY-2361-2.diff, DERBY-2361-2.zip, DERBY-2361-3.diff,
> DERBY-2361-4.diff, DERBY-2361-4.zip, 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.
