> It says: "Cannot find any provider supporting Blowfish". I'm using
> jdk-1.5.0_01 with Eclipse 3.0.1. I also had the 1.5 jre installed as
> well, but I uninstalled it to see if that made any difference. My
> java.security file is the default, and appears to specify all the
> normal security providers. I also have j2ee installed, but I don't see
> why that should cause any problems. Any help would be appreciated.
Try invoking from the command line. If this works, configure the settings
of your JRE in the Eclipse preferences (Preferences->Java->Installed
JREs->Configure) to "use system default libraries" I don't quite know what
causes this problem, but this fixes

Signature
In pioneer days they used oxen for heavy pulling, and when one ox
couldn't budge a log, they didn't try to grow a larger ox. We shouldn't
be trying for bigger computers, but for more systems of computers.
--- Rear Admiral Grace Murray Hopper
Roland - 04 Apr 2005 21:27 GMT
>>It says: "Cannot find any provider supporting Blowfish". I'm using
>>jdk-1.5.0_01 with Eclipse 3.0.1. I also had the 1.5 jre installed as
[quoted text clipped - 7 lines]
> JREs->Configure) to "use system default libraries" I don't quite know what
> causes this problem, but this fixes
If 'Use system libraries' is unchecked (off), Eclipse adds the
'-Xbootclasspath' parameter --with all the libs in the list-- to the
java executable.
If it is checked, Eclipse doesn't add -Xbootclasspath, so it allows the
java executable to discover its own boot classpath.

Signature
Regards,
Roland de Ruiter
___ ___
/__/ w_/ /__/
/ \ /_/ / \
David B. Held - 20 Apr 2005 23:16 GMT
> [...]
> If 'Use system libraries' is unchecked (off), Eclipse adds the
> '-Xbootclasspath' parameter --with all the libs in the list-- to the
> java executable.
> If it is checked, Eclipse doesn't add -Xbootclasspath, so it allows the
> java executable to discover its own boot classpath.
Thanks for the replies. It turns out that I had moved around my
JREs a bit and confused Eclipse. After getting all the paths
correct, I had to delete some files in a debug directory under
some configuration folder because they managed to store an absolute
path to the old JRE. Found that trick somewhere on the net. It
all works great now.
Dave