-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evan,
On 7/13/2009 7:08 PM, Evan Smith wrote:
> Case closed. Turns out my build was churning out both commons-net-1.4
> AND commons-net-2.0, resulting in a conflict.
That'll do it.
Good luck configuring all those security allowances :)
- -chris
---
Case closed. Turns out my build was churning out both commons-net-1.4
AND commons-net-2.0, resulting in a conflict. Hence, when I ran it
from Tomcat I saw the problem, and when I ran it from my test in
eclipse, I did not.
Thanks for your help Chris.
Evan
On Jul 13, 2009, at 2:10 PM, Evan
Holy smokes, the thing doesn't run at all if I turn the security
manager on. No doubt I should be running with one, but I'm afraid
that's chasing after an altogether different problem, at the moment.
I'm hesitant to go fix that until I've figured out this issue first.
Any other ideas?
Tha
Thanks for the response, Chris.
No security manager, as I'm running into the errors in dev. I will try
running it under a security manager, and explicitly configure
catalina.policy to account for this connection. I'll let you know what
I find.
Evan
On Jul 13, 2009, at 10:06 AM, Christop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evan,
On 7/10/2009 4:43 PM, Evan Smith wrote:
> What's puzzling is that I have tested this exact code inside and outside
> Tomcat, on several different machines. On every machine, it connects and
> lists files on the FTP server successfully every time
I have a Java 1.5 application hosted in Tomcat 5.5, and am using
Spring 2.0. The application has a wired controller that references an
instance of org.apache.commons.net.ftp.FTPSClient (commons-net-2.0).
On request, this controller should trigger a new FTP connection over
SSL to an externa
