I haven't look into the exact details on how to break out a FtpLet JAR,
but the start would be classes/interfaces in
org.apache.ftpserver.ftplet. That includes UserManager and
FileSystemManager.
/niklas
[EMAIL PROTECTED] wrote:
I would benefit from having separate jars as you describe. By FTPLet
interfaces, do you also mean the IFileManager and IUserManager?
Gary T. Mui * Vice President * SunGard Transaction Network * 445
Hamilton Avenue * 2nd Floor * White Plains, NY 10601
Tel 914-989-3118 * Fax 914-422-3693 * [EMAIL PROTECTED] *
www.sungard.com/stn
SunGard Institutional Brokerage Inc. * Member NASD/SIPC
CONFIDENTIALITY: This email (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this email in error,
please notify the sender and delete this email from your system. Thank
you.
-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Niklas Gustavsson
Sent: Thursday, August 17, 2006 11:06 AM
To: [email protected]
Subject: Splitting the code into seperate JARs
Hi
I know that this has been discussed before, but I'll give it another
try.
I would like to split the code into three deliverables (JARs):
* FTPlet interfaces
* Server implementation
* GUI
At least I would like to seperate the GUI from the rest as it would be
beneficial with a simple executable JAR for the GUI. Also, the GUI would
usually not be that useful on boxes where the server would be running
(probably on runlevel 3) but rather on a administers desktop (but we'll
need remote configuration for that of course).
I'll be happy to do the work as long as no one objects.
/niklas
