You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Niklas Gustavsson (JIRA)" <ji...@apache.org> on 2008/11/16 22:06:44 UTC

[jira] Closed: (FTPSERVER-218) Suggestion to enable user properties file to be updated without restarting server

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

Niklas Gustavsson closed FTPSERVER-218.
---------------------------------------

    Resolution: Fixed

Fixed in rev 718118.

> Suggestion to enable user properties file to be updated without restarting server
> ---------------------------------------------------------------------------------
>
>                 Key: FTPSERVER-218
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-218
>             Project: FtpServer
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0-M3
>         Environment: Windows XP, JRE 1.5.0_11
>            Reporter: Gary Bell
>            Assignee: Niklas Gustavsson
>             Fix For: 1.0-M4
>
>         Attachments: FTPSERVER-218-TEST.patch, FTPSERVER-218.patch
>
>
> Currently, there is no method by which manual updates to a "user list" properties file that backs the PropertiesUserManager class can be loaded into a running server. You have to stop and then restart the server to see any changes. 
> We are using FTPServer in embedded mode, and we need the site administrator to be able to hand-edit the file and then issue a custom function in our application to get the running server to reload the properties file. Prior to FTPServer-187, we handled this use case by creating a new instance of the PropertiesUserManager class using the newly-updated properties file and then calling server.getListener("default").setUserManager(...) .
> My suggestion is to add a refresh() method to the PropertiesUserManager class that will reload the properties file directly. Only new calls to getUserByName()  would return the updated information - existing BaseUser instances remain unchanged.

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