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] Commented: (DERBY-2489) Document the policy-reloading system procedure.
Date Wed, 28 Mar 2007 17:50:25 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484941

Kim Haase commented on DERBY-2489:

Thanks for this excellent documentation, Rick.

Just a few doc nits:


You might want to make the link to http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFiles.html
active by
wrapping it in 

<xref format="html" scope="external" xref="http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFiles.html">

The scope="external" attribute causes the link to open in a new browser window. I believe
that in other files in the Dev Guide there are URLs that are currently wrapped in <synph>
like this one, but that is not the preferred tag. 

In the last item under "Optional permissions," the correct manual name is "Reference Manual,"
not "Reference Guide". You might want to use the conrefs citation for this, similar to the
one for for Tuning Derby in the previous item.


I know you can't do an actual cross-reference, but you might want to refer people to the sections
in the Admin and Dev guides that discuss this subject.

> Document the policy-reloading system procedure.
> -----------------------------------------------
>                 Key: DERBY-2489
>                 URL: https://issues.apache.org/jira/browse/DERBY-2489
>             Project: Derby
>          Issue Type: New Feature
>          Components: Documentation
>            Reporter: Rick Hillegas
>         Assigned To: Rick Hillegas
>             Fix For:
>         Attachments: derby-2489-01-output.jar, derby-2489-01.diff
> Document SYSCS_RELOAD_SECURITY_POLICY, which was introduced by DERBY-2466. This includes
teasing apart the documentation of the Template and Basic policies.

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

View raw message