tags:

views:

159

answers:

3

I know 1.3 is old as dirt, but I don't have an option of doing a jvm upgrade at this point.

+2  A: 

Have you tried the 1.x branch of commons-net? I checked out the 1.5.0_RC4 tag, modified the build.xml to target 1.3 and it compiled OK. It might be worth a further look.

As a curiosity, what environment are you running in that keeps you locked in to a JVM version that has been EOL for years?

Kevin
Thanks, I'll take a look. The upgrade to the jvm is on the radar, but the app really hasn't changed in years and everything is working. If it ain't broke...
BillMan
+1  A: 

Just for the record. I believe the standard encryption stuff was not introduced until Java 1.4 (JSSE). Hence you will most likely need an separate JSSE implementation, which I do not know if will be available for your 1.3 platform (which is most likely an IBM one since it is hard to upgrade).

Thorbjørn Ravn Andersen
When JSSE is not an option then the Bouncy Castle Crypto API (http://www.bouncycastle.org/) is often very useful. I'd be surprised if it wouldn't run on Java 1.3 as well.
Joachim Sauer
I'm almost positive that Bouncy Castle runs on 1.3.
BillMan
A: 

All versions of edtFTPj/PRO except the latest run on 1.3. Let us know if you would like a version that does.

Bruce Blackshaw