On Wed, 04 Feb 2004 16:05:22 -0800 Mark Maxham <[EMAIL PROTECTED]> wrote:
> I have a very simple little program: > > I'm running kaffe 1.1.3 on Debian, and I have built the GNU Crypto from > the latest CVS, as well as Jessie, also from the latest CVS. Here's my > little test app: > > [ ... ] > > java -classpath .:/data/workdir/source/gnu-crypto.jar: > /data/workdir/jce/javax-crypto.jar: > /data/workdir/security/javax-security.jar: > /data/jessie-0.9.6/lib/javax-net.jar: > /data/jessie-0.9.6/lib/javax-security-cert.jar: > /data/jessie-0.9.6/lib/org-metastatic-jessie.jar HttpsTest > > I looked in the jessie.jar file and everything looks like it's there to > provide HTTPS, and I get this: > > java.net.MalformedURLException: Protocol handler not found: https > at java.net.URL.<init> (URL.java:430) > at java.net.URL.<init> (URL.java:311) > at HttpsTest.main (HttpsTest.java:17) > > I tried moving the jessie.jar into the BOOTCLASSPATH and got a whole new > raft of exceptions, because jessie wants to load some classes by name. > But to do so, it has to call [some object].class.getClassLoader(). But > if the calling class was loaded by the bootloader, getClassLoader() > returns null. Argh! It's like I'm stuck in a catch-22 here. > > Has anybody else made https work with jessie under kaffe? If so, what's > the trick? Looks like URL.getURLStreamHandler() is using the wrong classloader to load the class of the handler (patch is attached). Should I check it in and file a bug against classpath? Regards, Helmer
URL-patch
Description: Binary data