Re: AsyncWeb
Weird, perhaps infra cleaned the repository. I'm deploying a new snapshot, based on MINA 2.0.0-M3 . Julien On Sun, 31 Aug 2008 10:54:29 -0600 Kevin Williams [EMAIL PROTECTED] wrote: Last week I was able to use asyncweb 0.9.0-SNAPSHOT from the Maven repository. Today it doesn't appear to be there. Is asyncweb going to be source-only, or is this a problem with the repository? On Wed, Jul 30, 2008 at 12:25 PM, Kevin Williams [EMAIL PROTECTED] wrote: Hmmm, I just tried to re-compile and it seems to be fine now. On Wed, Jul 30, 2008 at 8:39 AM, Julien Vermillard [EMAIL PROTECTED] wrote: On Wed, 30 Jul 2008 08:31:30 -0600 Kevin Williams [EMAIL PROTECTED] wrote: Will AsyncWeb be part of the Mina 2.0 release? I'm curious to try using this as the basis for a JRuby web server. I tried checking out the source at http://svn.apache.org/repos/asf/mina/asyncweb/trunk/ but it didn't compile. Asyncweb got different release cycle than MINA, and nothing is planned for moment. Personnaly I concentrate on MINA, until 2.0 is on the rails. It's pity it's not having much visibility (website doc) because it's a nice piece of software easily embeddable in any kind of application, but I hope this will change :) I have no problem to recompile it (mvn clean install), you got the details of the error ? Julien -- Cheers, Kevin Williams http://bantamtech.com/ http://almostserio.us/ http://kevwil.com/ signature.asc Description: PGP signature
[jira] Created: (FTPSERVER-171) NativeFileSystemView.getFileObject(String file) and case sensitivity
NativeFileSystemView.getFileObject(String file) and case sensitivity Key: FTPSERVER-171 URL: https://issues.apache.org/jira/browse/FTPSERVER-171 Project: FtpServer Issue Type: Bug Components: Core Environment: Linux (or other case sensitive filesystems) Reporter: Carl Bunting Priority: Minor NativeFileSystemView.getFileObject(String file) currently doesn't pass the caseInsenstive instance variable to NativeFileObject.getPhysicalName(rootDir, currDir, file) As a result, Ftp GET arguments have to be in the correct case when the server is running on a case-sensitive filesystem. Changing it to NativeFileObject.getPhysicalName(rootDir, currDir, file, caseInsensitive) will resolve this. Regards, Carl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-171) NativeFileSystemView.getFileObject(String file) and case sensitivity
[ https://issues.apache.org/jira/browse/FTPSERVER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Bunting updated FTPSERVER-171: --- Attachment: NativeFileSystemView.java.patch attached patch.. NativeFileSystemView.getFileObject(String file) and case sensitivity Key: FTPSERVER-171 URL: https://issues.apache.org/jira/browse/FTPSERVER-171 Project: FtpServer Issue Type: Bug Components: Core Environment: Linux (or other case sensitive filesystems) Reporter: Carl Bunting Priority: Minor Attachments: NativeFileSystemView.java.patch Original Estimate: 0.17h Remaining Estimate: 0.17h NativeFileSystemView.getFileObject(String file) currently doesn't pass the caseInsenstive instance variable to NativeFileObject.getPhysicalName(rootDir, currDir, file) As a result, Ftp GET arguments have to be in the correct case when the server is running on a case-sensitive filesystem. Changing it to NativeFileObject.getPhysicalName(rootDir, currDir, file, caseInsensitive) will resolve this. Regards, Carl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FTPSERVER-172) Change org.apache.ftpserver.command.USER to use the User interface instead of the class BaseUser
Change org.apache.ftpserver.command.USER to use the User interface instead of the class BaseUser Key: FTPSERVER-172 URL: https://issues.apache.org/jira/browse/FTPSERVER-172 Project: FtpServer Issue Type: Bug Components: Core Reporter: Carl Bunting Priority: Minor Attachments: USER.java.patch Could org.apache.ftpserver.command.USER be changed so it uses the User interface instead of the class BaseUser please? It will allow users to write their own custom User implementations. Many thanks, Carl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-172) Change org.apache.ftpserver.command.USER to use the User interface instead of the class BaseUser
[ https://issues.apache.org/jira/browse/FTPSERVER-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Bunting updated FTPSERVER-172: --- Attachment: USER.java.patch attached patch Change org.apache.ftpserver.command.USER to use the User interface instead of the class BaseUser Key: FTPSERVER-172 URL: https://issues.apache.org/jira/browse/FTPSERVER-172 Project: FtpServer Issue Type: Bug Components: Core Reporter: Carl Bunting Priority: Minor Attachments: USER.java.patch Original Estimate: 0.17h Remaining Estimate: 0.17h Could org.apache.ftpserver.command.USER be changed so it uses the User interface instead of the class BaseUser please? It will allow users to write their own custom User implementations. Many thanks, Carl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FTPSERVER-172) Change org.apache.ftpserver.command.USER to use the User interface instead of the class BaseUser
[ https://issues.apache.org/jira/browse/FTPSERVER-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson closed FTPSERVER-172. --- Resolution: Fixed Fix Version/s: 1.0-M3 Assignee: Niklas Gustavsson Applied, thanks! svn -m USER command should not use BaseUser (FTPSERVER-172) commit Sendingapache/ftpserver/command/USER.java Transmitting file data . Committed revision 691038. Change org.apache.ftpserver.command.USER to use the User interface instead of the class BaseUser Key: FTPSERVER-172 URL: https://issues.apache.org/jira/browse/FTPSERVER-172 Project: FtpServer Issue Type: Bug Components: Core Reporter: Carl Bunting Assignee: Niklas Gustavsson Priority: Minor Fix For: 1.0-M3 Attachments: USER.java.patch Original Estimate: 0.17h Remaining Estimate: 0.17h Could org.apache.ftpserver.command.USER be changed so it uses the User interface instead of the class BaseUser please? It will allow users to write their own custom User implementations. Many thanks, Carl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FTPSERVER-171) NativeFileSystemView.getFileObject(String file) and case sensitivity
[ https://issues.apache.org/jira/browse/FTPSERVER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson closed FTPSERVER-171. --- Resolution: Fixed Fix Version/s: 1.0-M3 Assignee: Niklas Gustavsson Patch applied, thanks! svn -m File system case insensitivity not passed down to getPhysicalName when getting file (FTPSERVER-171) commit Sendingapache/ftpserver/filesystem/NativeFileSystemView.java Transmitting file data . Committed revision 691040. NativeFileSystemView.getFileObject(String file) and case sensitivity Key: FTPSERVER-171 URL: https://issues.apache.org/jira/browse/FTPSERVER-171 Project: FtpServer Issue Type: Bug Components: Core Environment: Linux (or other case sensitive filesystems) Reporter: Carl Bunting Assignee: Niklas Gustavsson Priority: Minor Fix For: 1.0-M3 Attachments: NativeFileSystemView.java.patch Original Estimate: 0.17h Remaining Estimate: 0.17h NativeFileSystemView.getFileObject(String file) currently doesn't pass the caseInsenstive instance variable to NativeFileObject.getPhysicalName(rootDir, currDir, file) As a result, Ftp GET arguments have to be in the correct case when the server is running on a case-sensitive filesystem. Changing it to NativeFileObject.getPhysicalName(rootDir, currDir, file, caseInsensitive) will resolve this. Regards, Carl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FTPSERVER-164) System out in FTPServer
[ https://issues.apache.org/jira/browse/FTPSERVER-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson closed FTPSERVER-164. --- Resolution: Fixed Fix Version/s: 1.0-M3 Assignee: Niklas Gustavsson Fixed (forgot to close issue) System out in FTPServer --- Key: FTPSERVER-164 URL: https://issues.apache.org/jira/browse/FTPSERVER-164 Project: FtpServer Issue Type: Bug Components: Server Affects Versions: 1.0-M2 Reporter: Claus Ibsen Assignee: Niklas Gustavsson Priority: Trivial Fix For: 1.0-M3 Hi We use FTPServer 1.0M2 as an embedded FTPServer for unit testing Apache Camel FTP component. Great work BTW: Example: Running org.apache.camel.component.file.remote.FromFtpMoveFileTest [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.188 sec We setup the FTPServer as: ftpServer = new FtpServer(); ftpServer.getListener(default).setPort(getPort()); ftpServer.start(); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FTPSERVER-152) NativeFileObject.hasDeletePermission() not working as expected.
[
https://issues.apache.org/jira/browse/FTPSERVER-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-152.
---
Resolution: Fixed
Patch commited. Thanks for both the patch and the test, great work!
svn -m Improve delete permission handling on native file system
(FTPSERVER-152). Patch by David Latorre commit
Sending
core/src/main/java/org/apache/ftpserver/filesystem/NativeFileObject.java
Sending
core/src/test/java/org/apache/ftpserver/filesystem/NativeFileObjectTest.java
Transmitting file data ..
Committed revision 691042.
NativeFileObject.hasDeletePermission() not working as expected.
Key: FTPSERVER-152
URL: https://issues.apache.org/jira/browse/FTPSERVER-152
Project: FtpServer
Issue Type: Bug
Affects Versions: 1.0-M2
Reporter: David Latorre
Assignee: Niklas Gustavsson
Fix For: 1.0-M3
Attachments: NativeFileObjectTest.patch
Original Estimate: 0.17h
Remaining Estimate: 0.17h
In the current implementation, hasDeletePermission in NativeFileObject
delegates to hasWritePermission in order to check whether a file can be
deleted or not. But, in most environments, a file can be deleted when it is
parent directory is writable, no matter if the file is writable itself or
not. I attach a fix which attempts to preserve both options: it will check
FTPServer's write permission for the actual file and if its parent directory
is writable.
public boolean hasDeletePermission() {
// root cannot be deleted
if (/.equals(fileName)) {
return false;
}
/* Added 12/08/2008: in the case that the permission is not
explicitly denied for this file
* we will check if the parent file has write permission as most
systems consider that a file can
* be deleted when their parent directory is writable.
*/
String fullName=getFullName();
// we check FTPServer's write permission for this file.
if (user.authorize(new WriteRequest(fullName)) == null) {
return false;
}
// In order to mantain consistency, when possible we delete the last
'/' character in the String
int indexOfSlash=fullName.lastIndexOf('/');
String parentFullName;
if (indexOfSlash==0){
parentFullName=/;
}
else{
parentFullName=fullName.substring(0,indexOfSlash);
}
// we check if the parent FileObject is writable.
NativeFileObject parentObject=new
NativeFileObject(parentFullName,file.getAbsoluteFile().getParentFile(),user);
return parentObject.hasWritePermission();
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-167) Overridable method to plug-in a password encryption mechanism for authentication
[ https://issues.apache.org/jira/browse/FTPSERVER-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson updated FTPSERVER-167: Assignee: Niklas Gustavsson Affects Version/s: (was: 1.0-M3) 1.0-M2 Overridable method to plug-in a password encryption mechanism for authentication Key: FTPSERVER-167 URL: https://issues.apache.org/jira/browse/FTPSERVER-167 Project: FtpServer Issue Type: New Feature Components: Core Affects Versions: 1.0-M2 Reporter: David Latorre Assignee: Niklas Gustavsson Priority: Minor Fix For: 1.0-M3 We need to use ftpserver against an existing database of users. The option to write custom SQL sentences works like a charm so our own difficulty is that passwords are encrypted in the database with a custom algorithm. There are a couple of ways to do that already , but it would be nice to have the possibility to provide our own password-processing method to the UserManager (so we don't have to create a custom UserManager). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FTPSERVER-167) Overridable method to plug-in a password encryption mechanism for authentication
[ https://issues.apache.org/jira/browse/FTPSERVER-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson closed FTPSERVER-167. --- Resolution: Fixed Fixed, interface now allows for plugging in a custom implementation for both PropertiesUserManager and DbUserManager Overridable method to plug-in a password encryption mechanism for authentication Key: FTPSERVER-167 URL: https://issues.apache.org/jira/browse/FTPSERVER-167 Project: FtpServer Issue Type: New Feature Components: Core Affects Versions: 1.0-M2 Reporter: David Latorre Assignee: Niklas Gustavsson Priority: Minor Fix For: 1.0-M3 We need to use ftpserver against an existing database of users. The option to write custom SQL sentences works like a charm so our own difficulty is that passwords are encrypted in the database with a custom algorithm. There are a couple of ways to do that already , but it would be nice to have the possibility to provide our own password-processing method to the UserManager (so we don't have to create a custom UserManager). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-161) Bundle-fy ftplet-api and code modules
[ https://issues.apache.org/jira/browse/FTPSERVER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson updated FTPSERVER-161: Fix Version/s: (was: 1.0-M3) 1.0-M4 Bundle-fy ftplet-api and code modules - Key: FTPSERVER-161 URL: https://issues.apache.org/jira/browse/FTPSERVER-161 Project: FtpServer Issue Type: New Feature Components: Core, Ftplets Affects Versions: 1.0-M2 Reporter: Niklas Gustavsson Assignee: Niklas Gustavsson Fix For: 1.0-M4 The ftplet-api and core modules should declare OSGi imports and exports to make FtpServer work in an OSGi environment -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-126) Perform some basic benchmarking and profiling of FtpServer
[ https://issues.apache.org/jira/browse/FTPSERVER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson updated FTPSERVER-126: Fix Version/s: (was: 1.0-M3) 1.0-M4 Perform some basic benchmarking and profiling of FtpServer -- Key: FTPSERVER-126 URL: https://issues.apache.org/jira/browse/FTPSERVER-126 Project: FtpServer Issue Type: Task Affects Versions: 1.0-M2 Reporter: Niklas Gustavsson Assignee: Niklas Gustavsson Fix For: 1.0-M4 Lots of code changes and an upgrade to MINA 2.0 has been done since we last did any benchmarking on FtpServer. These tests should be repeated on the new code base to find any obvious issues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-133) Profile leaking file handles
[ https://issues.apache.org/jira/browse/FTPSERVER-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson updated FTPSERVER-133: Fix Version/s: (was: 1.0-M3) 1.0-M4 Profile leaking file handles Key: FTPSERVER-133 URL: https://issues.apache.org/jira/browse/FTPSERVER-133 Project: FtpServer Issue Type: Task Components: Core Affects Versions: 1.0-M1, 1.0-M2 Reporter: Niklas Gustavsson Assignee: Niklas Gustavsson Fix For: 1.0-M4 There are indications of FtpServer not releasing file handles appropriately. This needs to be profiled and fixed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-159) Remove use of private commons-net repository
[ https://issues.apache.org/jira/browse/FTPSERVER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson updated FTPSERVER-159: Fix Version/s: (was: 1.0-M3) 1.0-M4 Remove use of private commons-net repository Key: FTPSERVER-159 URL: https://issues.apache.org/jira/browse/FTPSERVER-159 Project: FtpServer Issue Type: Improvement Components: Core Affects Versions: 1.0-M2 Reporter: Niklas Gustavsson Assignee: Niklas Gustavsson Fix For: 1.0-M4 We currently use our own commons-net repository, instead we should make sure Apache Commons publish a snapshot to the snapshot repos and use that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-160) Refactor package structure to remove cyclic dependencies and allow for OSGi export
[ https://issues.apache.org/jira/browse/FTPSERVER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Gustavsson updated FTPSERVER-160: Fix Version/s: (was: 1.0-M3) 1.0-M4 Refactor package structure to remove cyclic dependencies and allow for OSGi export -- Key: FTPSERVER-160 URL: https://issues.apache.org/jira/browse/FTPSERVER-160 Project: FtpServer Issue Type: Improvement Components: Core, Ftplets Affects Versions: 1.0-M2 Reporter: Niklas Gustavsson Assignee: Niklas Gustavsson Fix For: 1.0-M4 Our package structure is unorganized. We should separate classes into public and private to enable OSGi exports to be cleanly defined. Also, we should aim for removing cyclic dependencies between packages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] Releasing FtpServer 1.0.0-M3
Hi This is a vote for the next milestone release, 1.0.0-M3, of FtpServer, a subproject of MINA. The plan was for M3 to include some large changes, however, we have since M2 had some really great bug reports and feature requests, so a new milestone would help the community by getting a new baseline to work from. This means that a new milestone, M4, has been added to the plan and some of the larger changes has been moved to that. You can find the binaries, RAT reports and Maven artifacts here: http://people.apache.org/~ngn/ftpserver/1.0.0-M3-SNAPSHOT/ These files was built from the SVN revision 691050. Time to show your reviewing skills! [ ]: +1, Release FtpServer 1.0.0-M3 [ ]: 0, Abstain [ ]: -1, Don't release MINA 1.0.0-M3 /niklas
