Version: 3.2.0 (using KDE 3.2.0, SuSE) Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-192-default When calling a site on the Intranet of my company, the java-applet fails. The output on the Java-console is: Java VM version: 1.4.2 Java VM vendor: Sun Microsystems Inc. Proxy: localhost:9090 Class could not be loaded: Active Backtrace: java.lang.ClassNotFoundException: Active at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at org.kde.kjas.server.KJASAppletClassLoader.findClass(KJASAppletClassLoader.java:233) at org.kde.kjas.server.KJASAppletClassLoader.loadClass(KJASAppletClassLoader.java:274) at org.kde.kjas.server.KJASAppletStub$2.run(KJASAppletStub.java:163) at java.lang.Thread.run(Thread.java:534) Class could not be loaded: Version Backtrace: java.lang.ClassNotFoundException: Version at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at org.kde.kjas.server.KJASAppletClassLoader.findClass(KJASAppletClassLoader.java:233) at org.kde.kjas.server.KJASAppletClassLoader.loadClass(KJASAppletClassLoader.java:274) at org.kde.kjas.server.KJASAppletStub$2.run(KJASAppletStub.java:163) at java.lang.Thread.run(Thread.java:534)
Calling the same page with Mozilla works fine.
Did it work with an older KDE installation? You seem to use a proxy. Have you made any exceptions for your intranet web server? Does it work if you enable 'Use KIO' in the Java settings (make sure you restart konqueror)?
Oliver wrote: > I use the Webwasher by Siemens for filterirng advertisement. It is actually > deactivated for this site. But even if I deactivate it entirely and the > java-console does not mention the proxy, it does not work. It neverworked > before regardless of the KDE-version. > With KIO activated it worked!!!! What is KIO? Thanks for the tip! See http://www.arstechnica.com/reviews/004/software/kde-3.2/kde-3.2-07.html basically we let KDE IO layer do all the network stuff (and not java itself) Hopefully the 'Use KIO' option, which is new in KDE-3.2, fixes more than it breaks. And can become the default in KDE-3.3. I think it's cookie based authentication that broke this case, marking it duplicate of #31903 *** This bug has been marked as a duplicate of 31903 ***