Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 72595 invoked from network); 22 Mar 2007 13:39:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Mar 2007 13:39:55 -0000 Received: (qmail 36503 invoked by uid 500); 22 Mar 2007 13:40:01 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 36462 invoked by uid 500); 22 Mar 2007 13:40:01 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 36444 invoked by uid 99); 22 Mar 2007 13:40:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2007 06:40:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2007 06:39:52 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6ABF0714057 for ; Thu, 22 Mar 2007 06:39:32 -0700 (PDT) Message-ID: <31381477.1174570772433.JavaMail.jira@brutus> Date: Thu, 22 Mar 2007 06:39:32 -0700 (PDT) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2361) Documentation should give examples for using the different security mechanisms In-Reply-To: <16325213.1172000825524.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483142 ] Kim Haase commented on DERBY-2361: ---------------------------------- Those are excellent suggestions for retitling those two topics -- thanks. I will implement them and attach a new patch if the technical folks don't disagree. The reason the values aren't in numerical order is that the first two are the ones that users are likely to specify. The other two are there solely for completeness: ordinarily users don't specify them, because they are the defaults (depending on the user/password settings). Maybe I should create two separate lists to make this clear? I'll try that. I agree about the problem of the numbers at the beginning and discarded the definition list probably for the same reason you do. I'll try bold and see if that helps. Thanks for the great feedback. > 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.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.