db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Halley Pacheco de Oliveira (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1287) Derby Server and Administration Guide - Network client driver examples
Date Thu, 04 May 2006 16:19:17 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1287?page=all ]

Halley Pacheco de Oliveira updated DERBY-1287:

    Attachment: radminappsclientxmp.diff

The diff file, the diff HTMLized file and the new manual page.

> Derby Server and Administration Guide - Network client driver examples
> ----------------------------------------------------------------------
>          Key: DERBY-1287
>          URL: http://issues.apache.org/jira/browse/DERBY-1287
>      Project: Derby
>         Type: Improvement

>   Components: Documentation
>     Versions:
>  Environment:  DITA-sourced documentation
>     Reporter: Halley Pacheco de Oliveira
>     Priority: Minor
>      Fix For:
>  Attachments: radminappsclientxmp.diff, radminappsclientxmp.diff.html, radminappsclientxmp.html
> In this page is written:
> Example 1 [...]  It specifies the user and password URL attributes. You must set these
attributes before attempting to connect to the server.
> The problem is that it is not written in this guide how and where to set these attributes.
There are informations about the attributes derby.connection.requireAuthentication, derby.authentication.provider
and derby.user in many places in Derby manuals, but I couldn't find an example showing these
attributes together.
> These reasons made me decide to submit an improvement to this page adding a sample derby.properties
file that conforms to the examples shown, that would be:
> derby.connection.requireAuthentication=true
> derby.authentication.provider=BUILTIN
> derby.user.judy=no12see
> Most of the introductory text of the improved page was copied from "Enabling user authentication"
in Derby Developer's Guide, but I think it should be repeated in this guide.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message